Combining Power Saving Operation with Cell Dormancy

ABSTRACT

A base station transmits indications to a wireless device. The indications include: a wake-up indication indicating downlink control channel monitoring, for a plurality of cells, during a discontinuous reception (DRX) on duration of a DRX cycle; and a dormancy indication indicating a switching to a dormant bandwidth part of a cell, from the plurality of cells, to stop downlink control channel monitoring. During the DRX on duration and based on transmitting both the wake-up indication and the dormancy indication, the base station: stops transmitting a downlink control channel on the cell, while maintaining the cell activated; and receives a channel state information report for the dormant bandwidth part.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. Pat. Application No.17/400,424, filed Aug. 12, 2021, which is a continuation ofInternational Application No. PCT/US2020/053557, filed Sep. 30, 2020,which claims the benefit of U.S. Provisional Application No. 62/908,487,filed Sep. 30, 2019, the contents of each of which are herebyincorporated by reference in their entireties.

BRIEF DESCRIPTION OF THE DRAWINGS

Examples of several of the various embodiments of the present disclosureare described herein with reference to the drawings.

FIG. 1A and FIG. 1B illustrate example mobile communication networks inwhich embodiments of the present disclosure may be implemented.

FIG. 2A and FIG. 2B respectively illustrate a New Radio (NR) user planeand control plane protocol stack.

FIG. 3 illustrates an example of services provided between protocollayers of the NR user plane protocol stack of FIG. 2A.

FIG. 4A illustrates an example downlink data flow through the NR userplane protocol stack of FIG. 2A.

FIG. 4B illustrates an example format of a MAC subheader in a MAC PDU.

FIG. 5A and FIG. 5B respectively illustrate a mapping between logicalchannels, transport channels, and physical channels for the downlink anduplink.

FIG. 6 is an example diagram showing RRC state transitions of a UE.

FIG. 7 illustrates an example configuration of an NR frame into whichOFDM symbols are grouped.

FIG. 8 illustrates an example configuration of a slot in the time andfrequency domain for an NR carrier.

FIG. 9 illustrates an example of bandwidth adaptation using threeconfigured BWPs for an NR carrier.

FIG. 10A illustrates three carrier aggregation configurations with twocomponent carriers.

FIG. 10B illustrates an example of how aggregated cells may beconfigured into one or more PUCCH groups.

FIG. 11A illustrates an example of an SS/PBCH block structure andlocation.

FIG. 11B illustrates an example of CSI-RSs that are mapped in the timeand frequency domains.

FIG. 12A and FIG. 12B respectively illustrate examples of three downlinkand uplink beam management procedures.

FIG. 13A, FIG. 13B, and FIG. 13C respectively illustrate a four-stepcontention-based random access procedure, a two-step contention-freerandom access procedure, and another two-step random access procedure.

FIG. 14A illustrates an example of CORESET configurations for abandwidth part.

FIG. 14B illustrates an example of a CCE-to-REG mapping for DCItransmission on a CORESET and PDCCH processing.

FIG. 15 illustrates an example of a wireless device in communicationwith a base station.

FIG. 16A, FIG. 16B, FIG. 16C, and FIG. 16D illustrate example structuresfor uplink and downlink transmission.

FIG. 17A, FIG. 17B and FIG. 17C illustrate examples of MAC subheaders.

FIG. 18A illustrates an example of a DL MAC PDU.

FIG. 18B illustrates an example of an UL MAC PDU.

FIG. 19 illustrates an example of multiple LCIDs of downlink.

FIG. 20 illustrates an example of multiple LCIDs of uplink.

FIG. 21A and FIG. 21B illustrate examples of SCellactivation/deactivation MAC CEs.

FIG. 22A, FIG. 22B, and FIG. 22C illustrate examples of SCellhibernation MAC CEs.

FIG. 23 illustrates a BWP management as per an aspect of an exampleembodiment of the present disclosure.

FIG. 24 illustrates a DRX configuration as per an aspect of an exampleembodiment of the present disclosure.

FIG. 25 illustrates management DRX timer(s) as per an aspect of anexample embodiment of the present disclosure.

FIG. 26A and FIG. 26B illustrates a power saving mechanisms as peraspects of example embodiment of the present disclosure.

FIG. 27 illustrates a power saving mechanism as per an aspect of anexample embodiment of the present disclosure.

FIG. 28 illustrates a beam failure recovery on a SCell as per an aspectof an example embodiment of the present disclosure.

FIG. 29 illustrates a beam failure recovery on a SCell as per an aspectof an example embodiment of the present disclosure.

FIG. 30 illustrates an example flowchart of a method for beam failurerecovery on a SCell as per an aspect of an example embodiment of thepresent disclosure.

FIG. 31 illustrates a beam failure recovery on a SCell as per an aspectof an example embodiment of the present disclosure.

FIG. 32 illustrates a beam failure recovery on a SCell as per an aspectof an example embodiment of the present disclosure.

FIG. 33 illustrates an example flowchart of a method for SCell BFRprocedure as per an aspect of an example embodiment of the presentdisclosure.

FIG. 34 illustrates a wake-up operation and SCell dormancy management asper an aspect of an example embodiment of the present disclosure.

FIG. 35 illustrates a flowchart of a method for wake-up operation andSCell dormancy management as per an aspect of an example embodiment ofthe present disclosure.

FIG. 36 illustrates a wake-up operation and SCell dormancy management asper an aspect of an example embodiment of the present disclosure.

FIG. 37 illustrates a wake-up operation and SCell dormancy management asper an aspect of an example embodiment of the present disclosure.

FIG. 38 illustrates an example flowchart of a method for a wake-upoperation and SCell dormancy management as per an aspect of an exampleembodiment of the present disclosure.

FIG. 39 illustrates an example flowchart of a method for a wake-upoperation and SCell dormancy management as per an aspect of an exampleembodiment of the present disclosure.

DETAILED DESCRIPTION

In the present disclosure, various embodiments are presented as examplesof how the disclosed techniques may be implemented and/or how thedisclosed techniques may be practiced in environments and scenarios. Itwill be apparent to persons skilled in the relevant art that variouschanges in form and detail can be made therein without departing fromthe scope. In fact, after reading the description, it will be apparentto one skilled in the relevant art how to implement alternativeembodiments. The present embodiments should not be limited by any of thedescribed exemplary embodiments. The embodiments of the presentdisclosure will be described with reference to the accompanyingdrawings. Limitations, features, and/or elements from the disclosedexample embodiments may be combined to create further embodiments withinthe scope of the disclosure. Any figures which highlight thefunctionality and advantages, are presented for example purposes only.The disclosed architecture is sufficiently flexible and configurable,such that it may be utilized in ways other than that shown. For example,the actions listed in any flowchart may be re-ordered or only optionallyused in some embodiments.

Embodiments may be configured to operate as needed. The disclosedmechanism may be performed when certain criteria are met, for example,in a wireless device, a base station, a radio environment, a network, acombination of the above, and/or the like. Example criteria may bebased, at least in part, on for example, wireless device or network nodeconfigurations, traffic load, initial system set up, packet sizes,traffic characteristics, a combination of the above, and/or the like.When the one or more criteria are met, various example embodiments maybe applied. Therefore, it may be possible to implement exampleembodiments that selectively implement disclosed protocols.

A base station may communicate with a mix of wireless devices. Wirelessdevices and/or base stations may support multiple technologies, and/ormultiple releases of the same technology. Wireless devices may have somespecific capability(ies) depending on wireless device category and/orcapability(ies). When this disclosure refers to a base stationcommunicating with a plurality of wireless devices, this disclosure mayrefer to a subset of the total wireless devices in a coverage area. Thisdisclosure may refer to, for example, a plurality of wireless devices ofa given LTE or 5G release with a given capability and in a given sectorof the base station. The plurality of wireless devices in thisdisclosure may refer to a selected plurality of wireless devices, and/ora subset of total wireless devices in a coverage area which performaccording to disclosed methods, and/or the like. There may be aplurality of base stations or a plurality of wireless devices in acoverage area that may not comply with the disclosed methods, forexample, those wireless devices or base stations may perform based onolder releases of LTE or 5G technology.

In this disclosure, “a” and “an” and similar phrases are to beinterpreted as “at least one” and “one or more.” Similarly, any termthat ends with the suffix “(s)” is to be interpreted as “at least one”and “one or more.” In this disclosure, the term “may” is to beinterpreted as “may, for example.” In other words, the term “may” isindicative that the phrase following the term “may” is an example of oneof a multitude of suitable possibilities that may, or may not, beemployed by one or more of the various embodiments. The terms“comprises” and “consists of”, as used herein, enumerate one or morecomponents of the element being described. The term “comprises” isinterchangeable with “includes” and does not exclude unenumeratedcomponents from being included in the element being described. Bycontrast, “consists of” provides a complete enumeration of the one ormore components of the element being described. The term “based on”, asused herein, should be interpreted as “based at least in part on” ratherthan, for example, “based solely on”. The term “and/or” as used hereinrepresents any possible combination of enumerated elements. For example,“A, B, and/or C” may represent A; B; C; A and B; A and C; B and C; or A,B, and C.

If A and B are sets and every element of A is an element of B, A iscalled a subset of B. In this specification, only non-empty sets andsubsets are considered. For example, possible subsets of B = {cell1,cell2} are: {cell1}, {cell2}, and {cell1, cell2}. The phrase “based on”(or equally “based at least on”) is indicative that the phrase followingthe term “based on” is an example of one of a multitude of suitablepossibilities that may, or may not, be employed to one or more of thevarious embodiments. The phrase “in response to” (or equally “inresponse at least to”) is indicative that the phrase following thephrase “in response to” is an example of one of a multitude of suitablepossibilities that may, or may not, be employed to one or more of thevarious embodiments. The phrase “depending on” (or equally “depending atleast to”) is indicative that the phrase following the phrase “dependingon” is an example of one of a multitude of suitable possibilities thatmay, or may not, be employed to one or more of the various embodiments.The phrase “employing/using” (or equally “employing/using at least”) isindicative that the phrase following the phrase “employing/using” is anexample of one of a multitude of suitable possibilities that may, or maynot, be employed to one or more of the various embodiments.

The term configured may relate to the capacity of a device whether thedevice is in an operational or non-operational state. Configured mayrefer to specific settings in a device that effect the operationalcharacteristics of the device whether the device is in an operational ornon-operational state. In other words, the hardware, software, firmware,registers, memory values, and/or the like may be “configured” within adevice, whether the device is in an operational or nonoperational state,to provide the device with specific characteristics. Terms such as “acontrol message to cause in a device” may mean that a control messagehas parameters that may be used to configure specific characteristics ormay be used to implement certain actions in the device, whether thedevice is in an operational or non-operational state.

In this disclosure, parameters (or equally called, fields, orInformation elements: IEs) may comprise one or more information objects,and an information object may comprise one or more other objects. Forexample, if parameter (IE) N comprises parameter (IE) M, and parameter(IE) M comprises parameter (IE) K, and parameter (IE) K comprisesparameter (information element) J. Then, for example, N comprises K, andN comprises J. In an example embodiment, when one or more messagescomprise a plurality of parameters, it implies that a parameter in theplurality of parameters is in at least one of the one or more messages,but does not have to be in each of the one or more messages.

Many features presented are described as being optional through the useof “may” or the use of parentheses. For the sake of brevity andlegibility, the present disclosure does not explicitly recite each andevery permutation that may be obtained by choosing from the set ofoptional features. The present disclosure is to be interpreted asexplicitly disclosing all such permutations. For example, a systemdescribed as having three optional features may be embodied in sevenways, namely with just one of the three possible features, with any twoof the three possible features or with three of the three possiblefeatures.

Many of the elements described in the disclosed embodiments may beimplemented as modules. A module is defined here as an element thatperforms a defined function and has a defined interface to otherelements. The modules described in this disclosure may be implemented inhardware, software in combination with hardware, firmware, wetware (e.g.hardware with a biological element) or a combination thereof, which maybe behaviorally equivalent. For example, modules may be implemented as asoftware routine written in a computer language configured to beexecuted by a hardware machine (such as C, C++, Fortran, Java, Basic,Matlab or the like) or a modeling/simulation program such as Simulink,Stateflow, GNU Octave, or LabVIEWMathScript. It may be possible toimplement modules using physical hardware that incorporates discrete orprogrammable analog, digital and/or quantum hardware. Examples ofprogrammable hardware comprise: computers, microcontrollers,microprocessors, application-specific integrated circuits (ASICs); fieldprogrammable gate arrays (FPGAs); and complex programmable logic devices(CPLDs). Computers, microcontrollers and microprocessors are programmedusing languages such as assembly, C, C++ or the like. FPGAs, ASICs andCPLDs are often programmed using hardware description languages (HDL)such as VHSIC hardware description language (VHDL) or Verilog thatconfigure connections between internal hardware modules with lesserfunctionality on a programmable device. The mentioned technologies areoften used in combination to achieve the result of a functional module.

FIG. 1A illustrates an example of a mobile communication network 100 inwhich embodiments of the present disclosure may be implemented. Themobile communication network 100 may be, for example, a public landmobile network (PLMN) run by a network operator. As illustrated in FIG.1A, the mobile communication network 100 includes a core network (CN)102, a radio access network (RAN) 104, and a wireless device 106.

The CN 102 may provide the wireless device 106 with an interface to oneor more data networks (DNs), such as public DNs (e.g., the Internet),private DNs, and/or intra-operator DNs. As part of the interfacefunctionality, the CN 102 may set up end-to-end connections between thewireless device 106 and the one or more DNs, authenticate the wirelessdevice 106, and provide charging functionality.

The RAN 104 may connect the CN 102 to the wireless device 106 throughradio communications over an air interface. As part of the radiocommunications, the RAN 104 may provide scheduling, radio resourcemanagement, and retransmission protocols. The communication directionfrom the RAN 104 to the wireless device 106 over the air interface isknown as the downlink and the communication direction from the wirelessdevice 106 to the RAN 104 over the air interface is known as the uplink.Downlink transmissions may be separated from uplink transmissions usingfrequency division duplexing (FDD), time-division duplexing (TDD),and/or some combination of the two duplexing techniques.

The term wireless device may be used throughout this disclosure to referto and encompass any mobile device or fixed (non-mobile) device forwhich wireless communication is needed or usable. For example, awireless device may be a telephone, smart phone, tablet, computer,laptop, sensor, meter, wearable device, Internet of Things (IoT) device,vehicle road side unit (RSU), relay node, automobile, and/or anycombination thereof. The term wireless device encompasses otherterminology, including user equipment (UE), user terminal (UT), accessterminal (AT), mobile station, handset, wireless transmit and receiveunit (WTRU), and/or wireless communication device.

The RAN 104 may include one or more base stations (not shown). The termbase station may be used throughout this disclosure to refer to andencompass a Node B (associated with UMTS and/or 3G standards), anEvolved Node B (eNB, associated with E-UTRA and/or 4G standards), aremote radio head (RRH), a baseband processing unit coupled to one ormore RRHs, a repeater node or relay node used to extend the coveragearea of a donor node, a Next Generation Evolved Node B (ng-eNB), aGeneration Node B (gNB, associated with NR and/or 5G standards), anaccess point (AP, associated with, for example, WiFi or any othersuitable wireless communication standard), and/or any combinationthereof. A base station may comprise at least one gNB Central Unit(gNB-CU) and at least one a gNB Distributed Unit (gNB-DU).

A base station included in the RAN 104 may include one or more sets ofantennas for communicating with the wireless device 106 over the airinterface. For example, one or more of the base stations may includethree sets of antennas to respectively control three cells (or sectors).The size of a cell may be determined by a range at which a receiver(e.g., a base station receiver) can successfully receive thetransmissions from a transmitter (e.g., a wireless device transmitter)operating in the cell. Together, the cells of the base stations mayprovide radio coverage to the wireless device 106 over a wide geographicarea to support wireless device mobility.

In addition to three-sector sites, other implementations of basestations are possible. For example, one or more of the base stations inthe RAN 104 may be implemented as a sectored site with more or less thanthree sectors. One or more of the base stations in the RAN 104 may beimplemented as an access point, as a baseband processing unit coupled toseveral remote radio heads (RRHs), and/or as a repeater or relay nodeused to extend the coverage area of a donor node. A baseband processingunit coupled to RRHs may be part of a centralized or cloud RANarchitecture, where the baseband processing unit may be eithercentralized in a pool of baseband processing units or virtualized. Arepeater node may amplify and rebroadcast a radio signal received from adonor node. A relay node may perform the same/similar functions as arepeater node but may decode the radio signal received from the donornode to remove noise before amplifying and rebroadcasting the radiosignal.

The RAN 104 may be deployed as a homogenous network of macrocell basestations that have similar antenna patterns and similar high-leveltransmit powers. The RAN 104 may be deployed as a heterogeneous network.In heterogeneous networks, small cell base stations may be used toprovide small coverage areas, for example, coverage areas that overlapwith the comparatively larger coverage areas provided by macrocell basestations. The small coverage areas may be provided in areas with highdata traffic (or so-called “hotspots”) or in areas with weak macrocellcoverage. Examples of small cell base stations include, in order ofdecreasing coverage area, microcell base stations, picocell basestations, and femtocell base stations or home base stations.

The Third-Generation Partnership Project (3GPP) was formed in 1998 toprovide global standardization of specifications for mobilecommunication networks similar to the mobile communication network 100in FIG. 1A. To date, 3GPP has produced specifications for threegenerations of mobile networks: a third generation (3G) network known asUniversal Mobile Telecommunications System (UMTS), a fourth generation(4G) network known as Long-Term Evolution (LTE), and a fifth generation(5G) network known as 5G System (5GS). Embodiments of the presentdisclosure are described with reference to the RAN of a 3GPP 5G network,referred to as next-generation RAN (NG-RAN). Embodiments may beapplicable to RANs of other mobile communication networks, such as theRAN 104 in FIG. 1A, the RANs of earlier 3G and 4G networks, and those offuture networks yet to be specified (e.g., a 3GPP 6G network). NG-RANimplements 5G radio access technology known as New Radio (NR) and may beprovisioned to implement 4G radio access technology or other radioaccess technologies, including non-3GPP radio access technologies.

FIG. 1B illustrates another example mobile communication network 150 inwhich embodiments of the present disclosure may be implemented. Mobilecommunication network 150 may be, for example, a PLMN run by a networkoperator. As illustrated in FIG. 1B, mobile communication network 150includes a 5G core network (5G-CN) 152, an NG-RAN 154, and UEs 156A and156B (collectively UEs 156). These components may be implemented andoperate in the same or similar manner as corresponding componentsdescribed with respect to FIG. 1A.

The 5G-CN 152 provides the UEs 156 with an interface to one or more DNs,such as public DNs (e.g., the Internet), private DNs, and/orintra-operator DNs. As part of the interface functionality, the 5G-CN152 may set up end-to-end connections between the UEs 156 and the one ormore DNs, authenticate the UEs 156, and provide charging functionality.Compared to the CN of a 3GPP 4G network, the basis of the 5G-CN 152 maybe a service-based architecture. This means that the architecture of thenodes making up the 5G-CN 152 may be defined as network functions thatoffer services via interfaces to other network functions. The networkfunctions of the 5G-CN 152 may be implemented in several ways, includingas network elements on dedicated or shared hardware, as softwareinstances running on dedicated or shared hardware, or as virtualizedfunctions instantiated on a platform (e.g., a cloud-based platform).

As illustrated in FIG. 1B, the 5G-CN 152 includes an Access and MobilityManagement Function (AMF) 158A and a User Plane Function (UPF) 158B,which are shown as one component AMF/UPF 158 in FIG. 1B for ease ofillustration. The UPF 158B may serve as a gateway between the NG-RAN 154and the one or more DNs. The UPF 158B may perform functions such aspacket routing and forwarding, packet inspection and user plane policyrule enforcement, traffic usage reporting, uplink classification tosupport routing of traffic flows to the one or more DNs, quality ofservice (QoS) handling for the user plane (e.g., packet filtering,gating, uplink/downlink rate enforcement, and uplink trafficverification), downlink packet buffering, and downlink data notificationtriggering. The UPF 158B may serve as an anchor point forintra-/inter-Radio Access Technology (RAT) mobility, an externalprotocol (or packet) data unit (PDU) session point of interconnect tothe one or more DNs, and/or a branching point to support a multi-homedPDU session. The UEs 156 may be configured to receive services through aPDU session, which is a logical connection between a UE and a DN.

The AMF 158A may perform functions such as Non-Access Stratum (NAS)signaling termination, NAS signaling security, Access Stratum (AS)security control, inter-CN node signaling for mobility between 3GPPaccess networks, idle mode UE reachability (e.g., control and executionof paging retransmission), registration area management, intra-systemand inter-system mobility support, access authentication, accessauthorization including checking of roaming rights, mobility managementcontrol (subscription and policies), network slicing support, and/orsession management function (SMF) selection. NAS may refer to thefunctionality operating between a CN and a UE, and AS may refer to thefunctionality operating between the UE and a RAN.

The 5G-CN 152 may include one or more additional network functions thatare not shown in FIG. 1B for the sake of clarity. For example, the 5G-CN152 may include one or more of a Session Management Function (SMF), anNR Repository Function (NRF), a Policy Control Function (PCF), a NetworkExposure Function (NEF), a Unified Data Management (UDM), an ApplicationFunction (AF), and/or an Authentication Server Function (AUSF).

The NG-RAN 154 may connect the 5G-CN 152 to the UEs 156 through radiocommunications over the air interface. The NG-RAN 154 may include one ormore gNBs, illustrated as gNB 160A and gNB 160B (collectively gNBs 160)and/or one or more ng-eNBs, illustrated as ng-eNB 162A and ng-eNB 162B(collectively ng-eNBs 162). The gNBs 160 and ng-eNBs 162 may be moregenerically referred to as base stations. The gNBs 160 and ng-eNBs 162may include one or more sets of antennas for communicating with the UEs156 over an air interface. For example, one or more of the gNBs 160and/or one or more of the ng-eNBs 162 may include three sets of antennasto respectively control three cells (or sectors). Together, the cells ofthe gNBs 160 and the ng-eNBs 162 may provide radio coverage to the UEs156 over a wide geographic area to support UE mobility.

As shown in FIG. 1B, the gNBs 160 and/or the ng-eNBs 162 may beconnected to the 5G-CN 152 by means of an NG interface and to other basestations by an Xn interface. The NG and Xn interfaces may be establishedusing direct physical connections and/or indirect connections over anunderlying transport network, such as an internet protocol (IP)transport network. The gNBs 160 and/or the ng-eNBs 162 may be connectedto the UEs 156 by means of a Uu interface. For example, as illustratedin FIG. 1B, gNB 160A may be connected to the UE 156A by means of a Uuinterface. The NG, Xn, and Uu interfaces are associated with a protocolstack. The protocol stacks associated with the interfaces may be used bythe network elements in FIG. 1B to exchange data and signaling messagesand may include two planes: a user plane and a control plane. The userplane may handle data of interest to a user. The control plane mayhandle signaling messages of interest to the network elements.

The gNBs 160 and/or the ng-eNBs 162 may be connected to one or moreAMF/UPF functions of the 5G-CN 152, such as the AMF/UPF 158, by means ofone or more NG interfaces. For example, the gNB 160A may be connected tothe UPF 158B of the AMF/UPF 158 by means of an NG-User plane (NG-U)interface. The NG-U interface may provide delivery (e.g., non-guaranteeddelivery) of user plane PDUs between the gNB 160A and the UPF 158B. ThegNB 160A may be connected to the AMF 158A by means of an NG-Controlplane (NG-C) interface. The NG-C interface may provide, for example, NGinterface management, UE context management, UE mobility management,transport of NAS messages, paging, PDU session management, andconfiguration transfer and/or warning message transmission.

The gNBs 160 may provide NR user plane and control plane protocolterminations towards the UEs 156 over the Uu interface. For example, thegNB 160A may provide NR user plane and control plane protocolterminations toward the UE 156A over a Uu interface associated with afirst protocol stack. The ng-eNBs 162 may provide Evolved UMTSTerrestrial Radio Access (E-UTRA) user plane and control plane protocolterminations towards the UEs 156 over a Uu interface, where E-UTRArefers to the 3GPP 4G radio-access technology. For example, the ng-eNB162B may provide E-UTRA user plane and control plane protocolterminations towards the UE 156B over a Uu interface associated with asecond protocol stack.

The 5G-CN 152 was described as being configured to handle NR and 4Gradio accesses. It will be appreciated by one of ordinary skill in theart that it may be possible for NR to connect to a 4G core network in amode known as “non-standalone operation.” In non-standalone operation, a4G core network is used to provide (or at least support) control-planefunctionality (e.g., initial access, mobility, and paging). Althoughonly one AMF/UPF 158 is shown in FIG. 1B, one gNB or ng-eNB may beconnected to multiple AMF/UPF nodes to provide redundancy and/or to loadshare across the multiple AMF/UPF nodes.

As discussed, an interface (e.g., Uu, Xn, and NG interfaces) between thenetwork elements in FIG. 1B may be associated with a protocol stack thatthe network elements use to exchange data and signaling messages. Aprotocol stack may include two planes: a user plane and a control plane.The user plane may handle data of interest to a user, and the controlplane may handle signaling messages of interest to the network elements.

FIG. 2A and FIG. 2B respectively illustrate examples of NR user planeand NR control plane protocol stacks for the Uu interface that liesbetween a UE 210 and a gNB 220. The protocol stacks illustrated in FIG.2A and FIG. 2B may be the same or similar to those used for the Uuinterface between, for example, the UE 156A and the gNB 160A shown inFIG. 1B.

FIG. 2A illustrates a NR user plane protocol stack comprising fivelayers implemented in the UE 210 and the gNB 220. At the bottom of theprotocol stack, physical layers (PHYs) 211 and 221 may provide transportservices to the higher layers of the protocol stack and may correspondto layer 1 of the Open Systems Interconnection (OSI) model. The nextfour protocols above PHYs 211 and 221 comprise media access controllayers (MACs) 212 and 222, radio link control layers (RLCs) 213 and 223,packet data convergence protocol layers (PDCPs) 214 and 224, and servicedata application protocol layers (SDAPs) 215 and 225. Together, thesefour protocols may make up layer 2, or the data link layer, of the OSImodel.

FIG. 3 illustrates an example of services provided between protocollayers of the NR user plane protocol stack. Starting from the top ofFIG. 2A and FIG. 3 , the SDAPs 215 and 225 may perform QoS flowhandling. The UE 210 may receive services through a PDU session, whichmay be a logical connection between the UE 210 and a DN. The PDU sessionmay have one or more QoS flows. A UPF of a CN (e.g., the UPF 158B) maymap IP packets to the one or more QoS flows of the PDU session based onQoS requirements (e.g., in terms of delay, data rate, and/or errorrate). The SDAPs 215 and 225 may perform mapping/de-mapping between theone or more QoS flows and one or more data radio bearers. Themapping/de-mapping between the QoS flows and the data radio bearers maybe determined by the SDAP 225 at the gNB 220. The SDAP 215 at the UE 210may be informed of the mapping between the QoS flows and the data radiobearers through reflective mapping or control signaling received fromthe gNB 220. For reflective mapping, the SDAP 225 at the gNB 220 maymark the downlink packets with a QoS flow indicator (QFI), which may beobserved by the SDAP 215 at the UE 210 to determine themapping/de-mapping between the QoS flows and the data radio bearers.

The PDCPs 214 and 224 may perform header compression/decompression toreduce the amount of data that needs to be transmitted over the airinterface, ciphering/deciphering to prevent unauthorized decoding ofdata transmitted over the air interface, and integrity protection (toensure control messages originate from intended sources. The PDCPs 214and 224 may perform retransmissions of undelivered packets, in-sequencedelivery and reordering of packets, and removal of packets received induplicate due to, for example, an intra-gNB handover. The PDCPs 214 and224 may perform packet duplication to improve the likelihood of thepacket being received and, at the receiver, remove any duplicatepackets. Packet duplication may be useful for services that require highreliability.

Although not shown in FIG. 3 , PDCPs 214 and 224 may performmapping/de-mapping between a split radio bearer and RLC channels in adual connectivity scenario. Dual connectivity is a technique that allowsa UE to connect to two cells or, more generally, two cell groups: amaster cell group (MCG) and a secondary cell group (SCG). A split beareris when a single radio bearer, such as one of the radio bearers providedby the PDCPs 214 and 224 as a service to the SDAPs 215 and 225, ishandled by cell groups in dual connectivity. The PDCPs 214 and 224 maymap/de-map the split radio bearer between RLC channels belonging to cellgroups.

The RLCs 213 and 223 may perform segmentation, retransmission throughAutomatic Repeat Request (ARQ), and removal of duplicate data unitsreceived from MACs 212 and 222, respectively. The RLCs 213 and 223 maysupport three transmission modes: transparent mode (TM); unacknowledgedmode (UM); and acknowledged mode (AM). Based on the transmission mode anRLC is operating, the RLC may perform one or more of the notedfunctions. The RLC configuration may be per logical channel with nodependency on numerologies and/or Transmission Time Interval (TTI)durations. As shown in FIG. 3 , the RLCs 213 and 223 may provide RLCchannels as a service to PDCPs 214 and 224, respectively.

The MACs 212 and 222 may perform multiplexing/demultiplexing of logicalchannels and/or mapping between logical channels and transport channels.The multiplexing/demultiplexing may include multiplexing/demultiplexingof data units, belonging to the one or more logical channels, into/fromTransport Blocks (TBs) delivered to/from the PHYs 211 and 221. The MAC222 may be configured to perform scheduling, scheduling informationreporting, and priority handling between UEs by means of dynamicscheduling. Scheduling may be performed in the gNB 220 (at the MAC 222)for downlink and uplink. The MACs 212 and 222 may be configured toperform error correction through Hybrid Automatic Repeat Request (HARQ)(e.g., one HARQ entity per carrier in case of Carrier Aggregation (CA)),priority handling between logical channels of the UE 210 by means oflogical channel prioritization, and/or padding. The MACs 212 and 222 maysupport one or more numerologies and/or transmission timings. In anexample, mapping restrictions in a logical channel prioritization maycontrol which numerology and/or transmission timing a logical channelmay use. As shown in FIG. 3 , the MACs 212 and 222 may provide logicalchannels as a service to the RLCs 213 and 223.

The PHYs 211 and 221 may perform mapping of transport channels tophysical channels and digital and analog signal processing functions forsending and receiving information over the air interface. These digitaland analog signal processing functions may include, for example,coding/decoding and modulation/demodulation. The PHYs 211 and 221 mayperform multi-antenna mapping. As shown in FIG. 3 , the PHYs 211 and 221may provide one or more transport channels as a service to the MACs 212and 222.

FIG. 4A illustrates an example downlink data flow through the NR userplane protocol stack. FIG. 4A illustrates a downlink data flow of threeIP packets (n, n+1, and m) through the NR user plane protocol stack togenerate two TBs at the gNB 220. An uplink data flow through the NR userplane protocol stack may be similar to the downlink data flow depictedin FIG. 4A.

The downlink data flow of FIG. 4A begins when SDAP 225 receives thethree IP packets from one or more QoS flows and maps the three packetsto radio bearers. In FIG. 4A, the SDAP 225 maps IP packets n and n+1 toa first radio bearer 402 and maps IP packet m to a second radio bearer404. An SDAP header (labeled with an “H” in FIG. 4A) is added to an IPpacket. The data unit from/to a higher protocol layer is referred to asa service data unit (SDU) of the lower protocol layer and the data unitto/from a lower protocol layer is referred to as a protocol data unit(PDU) of the higher protocol layer. As shown in FIG. 4A, the data unitfrom the SDAP 225 is an SDU of lower protocol layer PDCP 224 and is aPDU of the SDAP 225.

The remaining protocol layers in FIG. 4A may perform their associatedfunctionality (e.g., with respect to FIG. 3 ), add correspondingheaders, and forward their respective outputs to the next lower layer.For example, the PDCP 224 may perform IP-header compression andciphering and forward its output to the RLC 223. The RLC 223 mayoptionally perform segmentation (e.g., as shown for IP packet m in FIG.4A) and forward its output to the MAC 222. The MAC 222 may multiplex anumber of RLC PDUs and may attach a MAC subheader to an RLC PDU to forma transport block. In NR, the MAC subheaders may be distributed acrossthe MAC PDU, as illustrated in FIG. 4A. In LTE, the MAC subheaders maybe entirely located at the beginning of the MAC PDU. The NR MAC PDUstructure may reduce processing time and associated latency because theMAC PDU subheaders may be computed before the full MAC PDU is assembled.

FIG. 4B illustrates an example format of a MAC subheader in a MAC PDU.The MAC subheader includes: an SDU length field for indicating thelength (e.g., in bytes) of the MAC SDU to which the MAC subheadercorresponds; a logical channel identifier (LCID) field for identifyingthe logical channel from which the MAC SDU originated to aid in thedemultiplexing process; a flag (F) for indicating the size of the SDUlength field; and a reserved bit (R) field for future use.

FIG. 4B further illustrates MAC control elements (CEs) inserted into theMAC PDU by a MAC, such as MAC 223 or MAC 222. For example, FIG. 4Billustrates two MAC CEs inserted into the MAC PDU. MAC CEs may beinserted at the beginning of a MAC PDU for downlink transmissions (asshown in FIG. 4B) and at the end of a MAC PDU for uplink transmissions.MAC CEs may be used for in-band control signaling. Example MAC CEsinclude: scheduling-related MAC CEs, such as buffer status reports andpower headroom reports; activation/deactivation MAC CEs, such as thosefor activation/deactivation of PDCP duplication detection, channel stateinformation (CSI) reporting, sounding reference signal (SRS)transmission, and prior configured components; discontinuous reception(DRX) related MAC CEs; timing advance MAC CEs; and random access relatedMAC CEs. A MAC CE may be preceded by a MAC subheader with a similarformat as described for MAC SDUs and may be identified with a reservedvalue in the LCID field that indicates the type of control informationincluded in the MAC CE.

Before describing the NR control plane protocol stack, logical channels,transport channels, and physical channels are first described as well asa mapping between the channel types. One or more of the channels may beused to carry out functions associated with the NR control planeprotocol stack described later below.

FIG. 5A and FIG. 5B illustrate, for downlink and uplink respectively, amapping between logical channels, transport channels, and physicalchannels. Information is passed through channels between the RLC, theMAC, and the PHY of the NR protocol stack. A logical channel may be usedbetween the RLC and the MAC and may be classified as a control channelthat carries control and configuration information in the NR controlplane or as a traffic channel that carries data in the NR user plane. Alogical channel may be classified as a dedicated logical channel that isdedicated to a specific UE or as a common logical channel that may beused by more than one UE. A logical channel may also be defined by thetype of information it carries. The set of logical channels defined byNR include, for example:

-   a paging control channel (PCCH) for carrying paging messages used to    page a UE whose location is not known to the network on a cell    level;-   a broadcast control channel (BCCH) for carrying system information    messages in the form of a master information block (MIB) and several    system information blocks (SIBs), wherein the system information    messages may be used by the UEs to obtain information about how a    cell is configured and how to operate within the cell;-   a common control channel (CCCH) for carrying control messages    together with random access;-   a dedicated control channel (DCCH) for carrying control messages    to/from a specific the UE to configure the UE; and-   a dedicated traffic channel (DTCH) for carrying user data to/from a    specific the UE.

Transport channels are used between the MAC and PHY layers and may bedefined by how the information they carry is transmitted over the airinterface. The set of transport channels defined by NR include, forexample:

-   a paging channel (PCH) for carrying paging messages that originated    from the PCCH;-   a broadcast channel (BCH) for carrying the MIB from the BCCH;-   a downlink shared channel (DL-SCH) for carrying downlink data and    signaling messages, including the SIBs from the BCCH;-   an uplink shared channel (UL-SCH) for carrying uplink data and    signaling messages; and-   a random access channel (RACH) for allowing a UE to contact the    network without any prior scheduling.

The PHY may use physical channels to pass information between processinglevels of the PHY. A physical channel may have an associated set oftime-frequency resources for carrying the information of one or moretransport channels. The PHY may generate control information to supportthe low-level operation of the PHY and provide the control informationto the lower levels of the PHY via physical control channels, known asL1/L2 control channels. The set of physical channels and physicalcontrol channels defined by NR include, for example:

-   a physical broadcast channel (PBCH) for carrying the MIB from the    BCH;-   a physical downlink shared channel (PDSCH) for carrying downlink    data and signaling messages from the DL-SCH, as well as paging    messages from the PCH;-   a physical downlink control channel (PDCCH) for carrying downlink    control information (DCI), which may include downlink scheduling    commands, uplink scheduling grants, and uplink power control    commands;-   a physical uplink shared channel (PUSCH) for carrying uplink data    and signaling messages from the UL-SCH and in some instances uplink    control information (UCI) as described below;-   a physical uplink control channel (PUCCH) for carrying UCI, which    may include HARQ acknowledgments, channel quality indicators (CQI),    pre-coding matrix indicators (PMI), rank indicators (RI), and    scheduling requests (SR); and-   a physical random access channel (PRACH) for random access.

Similar to the physical control channels, the physical layer generatesphysical signals to support the low-level operation of the physicallayer. As shown in FIG. 5A and FIG. 5B, the physical layer signalsdefined by NR include: primary synchronization signals (PSS), secondarysynchronization signals (SSS), channel state information referencesignals (CSI-RS), demodulation reference signals (DMRS), soundingreference signals (SRS), and phase-tracking reference signals (PT-RS).These physical layer signals will be described in greater detail below.

FIG. 2B illustrates an example NR control plane protocol stack. As shownin FIG. 2B, the NR control plane protocol stack may use the same/similarfirst four protocol layers as the example NR user plane protocol stack.These four protocol layers include the PHYs 211 and 221, the MACs 212and 222, the RLCs 213 and 223, and the PDCPs 214 and 224. Instead ofhaving the SDAPs 215 and 225 at the top of the stack as in the NR userplane protocol stack, the NR control plane stack has radio resourcecontrols (RRCs) 216 and 226 and NAS protocols 217 and 237 at the top ofthe NR control plane protocol stack.

The NAS protocols 217 and 237 may provide control plane functionalitybetween the UE 210 and the AMF 230 (e.g., the AMF 158A) or, moregenerally, between the UE 210 and the CN. The NAS protocols 217 and 237may provide control plane functionality between the UE 210 and the AMF230 via signaling messages, referred to as NAS messages. There is nodirect path between the UE 210 and the AMF 230 through which the NASmessages can be transported. The NAS messages may be transported usingthe AS of the Uu and NG interfaces. NAS protocols 217 and 237 mayprovide control plane functionality such as authentication, security,connection setup, mobility management, and session management.

The RRCs 216 and 226 may provide control plane functionality between theUE 210 and the gNB 220 or, more generally, between the UE 210 and theRAN. The RRCs 216 and 226 may provide control plane functionalitybetween the UE 210 and the gNB 220 via signaling messages, referred toas RRC messages. RRC messages may be transmitted between the UE 210 andthe RAN using signaling radio bearers and the same/similar PDCP, RLC,MAC, and PHY protocol layers. The MAC may multiplex control-plane anduser-plane data into the same transport block (TB). The RRCs 216 and 226may provide control plane functionality such as: broadcast of systeminformation related to AS and NAS; paging initiated by the CN or theRAN; establishment, maintenance and release of an RRC connection betweenthe UE 210 and the RAN; security functions including key management;establishment, configuration, maintenance and release of signaling radiobearers and data radio bearers; mobility functions; QoS managementfunctions; the UE measurement reporting and control of the reporting;detection of and recovery from radio link failure (RLF); and/or NASmessage transfer. As part of establishing an RRC connection, RRCs 216and 226 may establish an RRC context, which may involve configuringparameters for communication between the UE 210 and the RAN.

FIG. 6 is an example diagram showing RRC state transitions of a UE. TheUE may be the same or similar to the wireless device 106 depicted inFIG. 1A, the UE 210 depicted in FIG. 2A and FIG. 2B, or any otherwireless device described in the present disclosure. As illustrated inFIG. 6 , a UE may be in at least one of three RRC states: RRC connected602 (e.g., RRC_CONNECTED), RRC idle 604 (e.g., RRC_IDLE), and RRCinactive 606 (e.g., RRC_INACTIVE).

In RRC connected 602, the UE has an established RRC context and may haveat least one RRC connection with a base station. The base station may besimilar to one of the one or more base stations included in the RAN 104depicted in FIG. 1A, one of the gNBs 160 or ng-eNBs 162 depicted in FIG.1B, the gNB 220 depicted in FIG. 2A and FIG. 2B, or any other basestation described in the present disclosure. The base station with whichthe UE is connected may have the RRC context for the UE. The RRCcontext, referred to as the UE context, may comprise parameters forcommunication between the UE and the base station. These parameters mayinclude, for example: one or more AS contexts; one or more radio linkconfiguration parameters; bearer configuration information (e.g.,relating to a data radio bearer, signaling radio bearer, logicalchannel, QoS flow, and/or PDU session); security information; and/orPHY, MAC, RLC, PDCP, and/or SDAP layer configuration information. Whilein RRC connected 602, mobility of the UE may be managed by the RAN(e.g., the RAN 104 or the NG-RAN 154). The UE may measure the signallevels (e.g., reference signal levels) from a serving cell andneighboring cells and report these measurements to the base stationcurrently serving the UE. The UE’s serving base station may request ahandover to a cell of one of the neighboring base stations based on thereported measurements. The RRC state may transition from RRC connected602 to RRC idle 604 through a connection release procedure 608 or to RRCinactive 606 through a connection inactivation procedure 610.

In RRC idle 604, an RRC context may not be established for the UE. InRRC idle 604, the UE may not have an RRC connection with the basestation. While in RRC idle 604, the UE may be in a sleep state for themajority of the time (e.g., to conserve battery power). The UE may wakeup periodically (e.g., once in every discontinuous reception cycle) tomonitor for paging messages from the RAN. Mobility of the UE may bemanaged by the UE through a procedure known as cell reselection. The RRCstate may transition from RRC idle 604 to RRC connected 602 through aconnection establishment procedure 612, which may involve a randomaccess procedure as discussed in greater detail below.

In RRC inactive 606, the RRC context previously established ismaintained in the UE and the base station. This allows for a fasttransition to RRC connected 602 with reduced signaling overhead ascompared to the transition from RRC idle 604 to RRC connected 602. Whilein RRC inactive 606, the UE may be in a sleep state and mobility of theUE may be managed by the UE through cell reselection. The RRC state maytransition from RRC inactive 606 to RRC connected 602 through aconnection resume procedure 614 or to RRC idle 604 though a connectionrelease procedure 616 that may be the same as or similar to connectionrelease procedure 608.

An RRC state may be associated with a mobility management mechanism. InRRC idle 604 and RRC inactive 606, mobility is managed by the UE throughcell reselection. The purpose of mobility management in RRC idle 604 andRRC inactive 606 is to allow the network to be able to notify the UE ofan event via a paging message without having to broadcast the pagingmessage over the entire mobile communications network. The mobilitymanagement mechanism used in RRC idle 604 and RRC inactive 606 may allowthe network to track the UE on a cell-group level so that the pagingmessage may be broadcast over the cells of the cell group that the UEcurrently resides within instead of the entire mobile communicationnetwork. The mobility management mechanisms for RRC idle 604 and RRCinactive 606 track the UE on a cell-group level. They may do so usingdifferent granularities of grouping. For example, there may be threelevels of cell-grouping granularity: individual cells; cells within aRAN area identified by a RAN area identifier (RAI); and cells within agroup of RAN areas, referred to as a tracking area and identified by atracking area identifier (TAI).

Tracking areas may be used to track the UE at the CN level. The CN(e.g., the CN 102 or the 5G-CN 152) may provide the UE with a list ofTAIs associated with a UE registration area. If the UE moves, throughcell reselection, to a cell associated with a TAI not included in thelist of TAIs associated with the UE registration area, the UE mayperform a registration update with the CN to allow the CN to update theUE’s location and provide the UE with a new the UE registration area.

RAN areas may be used to track the UE at the RAN level. For a UE in RRCinactive 606 state, the UE may be assigned a RAN notification area. ARAN notification area may comprise one or more cell identities, a listof RAIs, or a list of TAIs. In an example, a base station may belong toone or more RAN notification areas. In an example, a cell may belong toone or more RAN notification areas. If the UE moves, through cellreselection, to a cell not included in the RAN notification areaassigned to the UE, the UE may perform a notification area update withthe RAN to update the UE’s RAN notification area.

A base station storing an RRC context for a UE or a last serving basestation of the UE may be referred to as an anchor base station. Ananchor base station may maintain an RRC context for the UE at leastduring a period of time that the UE stays in a RAN notification area ofthe anchor base station and/or during a period of time that the UE staysin RRC inactive 606.

A gNB, such as gNBs 160 in FIG. 1B, may be split in two parts: a centralunit (gNB-CU), and one or more distributed units (gNB-DU). A gNB-CU maybe coupled to one or more gNB-DUs using an F1 interface. The gNB-CU maycomprise the RRC, the PDCP, and the SDAP. A gNB-DU may comprise the RLC,the MAC, and the PHY.

In NR, the physical signals and physical channels (discussed withrespect to FIG. 5A and FIG. 5B) may be mapped onto orthogonal frequencydivisional multiplexing (OFDM) symbols. OFDM is a multicarriercommunication scheme that transmits data over F orthogonal subcarriers(or tones). Before transmission, the data may be mapped to a series ofcomplex symbols (e.g., M-quadrature amplitude modulation (M-QAM) orM-phase shift keying (M-PSK) symbols), referred to as source symbols,and divided into F parallel symbol streams. The F parallel symbolstreams may be treated as though they are in the frequency domain andused as inputs to an Inverse Fast Fourier Transform (IFFT) block thattransforms them into the time domain. The IFFT block may take in Fsource symbols at a time, one from each of the F parallel symbolstreams, and use each source symbol to modulate the amplitude and phaseof one of F sinusoidal basis functions that correspond to the Forthogonal subcarriers. The output of the IFFT block may be Ftime-domain samples that represent the summation of the F orthogonalsubcarriers. The F time-domain samples may form a single OFDM symbol.After some processing (e.g., addition of a cyclic prefix) andup-conversion, an OFDM symbol provided by the IFFT block may betransmitted over the air interface on a carrier frequency. The Fparallel symbol streams may be mixed using an FFT block before beingprocessed by the IFFT block. This operation produces Discrete FourierTransform (DFT)-precoded OFDM symbols and may be used by UEs in theuplink to reduce the peak to average power ratio (PAPR). Inverseprocessing may be performed on the OFDM symbol at a receiver using anFFT block to recover the data mapped to the source symbols.

FIG. 7 illustrates an example configuration of an NR frame into whichOFDM symbols are grouped. An NR frame may be identified by a systemframe number (SFN). The SFN may repeat with a period of 1024 frames. Asillustrated, one NR frame may be 10 milliseconds (ms) in duration andmay include 10 subframes that are 1 ms in duration. A subframe may bedivided into slots that include, for example, 14 OFDM symbols per slot.

The duration of a slot may depend on the numerology used for the OFDMsymbols of the slot. In NR, a flexible numerology is supported toaccommodate different cell deployments (e.g., cells with carrierfrequencies below 1 GHz up to cells with carrier frequencies in themm-wave range). A numerology may be defined in terms of subcarrierspacing and cyclic prefix duration. For a numerology in NR, subcarrierspacings may be scaled up by powers of two from a baseline subcarrierspacing of 15 kHz, and cyclic prefix durations may be scaled down bypowers of two from a baseline cyclic prefix duration of 4.7 µs. Forexample, NR defines numerologies with the following subcarrierspacing/cyclic prefix duration combinations: 15 kHz/4.7 µs; 30 kHz/2.3µs; 60 kHz/1.22 µs; 120 kHz/0.59 µs; and 240 kHz/0.29 µs.

A slot may have a fixed number of OFDM symbols (e.g., 14 OFDM symbols).A numerology with a higher subcarrier spacing has a shorter slotduration and, correspondingly, more slots per subframe. FIG. 7illustrates this numerology-dependent slot duration andslots-per-subframe transmission structure (the numerology with asubcarrier spacing of 240 kHz is not shown in FIG. 7 for ease ofillustration). A subframe in NR may be used as a numerology-independenttime reference, while a slot may be used as the unit upon which uplinkand downlink transmissions are scheduled. To support low latency,scheduling in NR may be decoupled from the slot duration and start atany OFDM symbol and last for as many symbols as needed for atransmission. These partial slot transmissions may be referred to asmini-slot or subslot transmissions.

FIG. 8 illustrates an example configuration of a slot in the time andfrequency domain for an NR carrier. The slot includes resource elements(REs) and resource blocks (RBs). An RE is the smallest physical resourcein NR. An RE spans one OFDM symbol in the time domain by one subcarrierin the frequency domain as shown in FIG. 8 . An RB spans twelveconsecutive REs in the frequency domain as shown in FIG. 8 . An NRcarrier may be limited to a width of 275 RBs or 275×12 = 3300subcarriers. Such a limitation, if used, may limit the NR carrier to 50,100, 200, and 400 MHz for subcarrier spacings of 15, 30, 60, and 120kHz, respectively, where the 400 MHz bandwidth may be set based on a 400MHz per carrier bandwidth limit.

FIG. 8 illustrates a single numerology being used across the entirebandwidth of the NR carrier. In other example configurations, multiplenumerologies may be supported on the same carrier.

NR may support wide carrier bandwidths (e.g., up to 400 MHz for asubcarrier spacing of 120 kHz). Not all UEs may be able to receive thefull carrier bandwidth (e.g., due to hardware limitations). Also,receiving the full carrier bandwidth may be prohibitive in terms of UEpower consumption. In an example, to reduce power consumption and/or forother purposes, a UE may adapt the size of the UE’s receive bandwidthbased on the amount of traffic the UE is scheduled to receive. This isreferred to as bandwidth adaptation.

NR defines bandwidth parts (BWPs) to support UEs not capable ofreceiving the full carrier bandwidth and to support bandwidthadaptation. In an example, a BWP may be defined by a subset ofcontiguous RBs on a carrier. A UE may be configured (e.g., via RRClayer) with one or more downlink BWPs and one or more uplink BWPs perserving cell (e.g., up to four downlink BWPs and up to four uplink BWPsper serving cell). At a given time, one or more of the configured BWPsfor a serving cell may be active. These one or more BWPs may be referredto as active BWPs of the serving cell. When a serving cell is configuredwith a secondary uplink carrier, the serving cell may have one or morefirst active BWPs in the uplink carrier and one or more second activeBWPs in the secondary uplink carrier.

For unpaired spectra, a downlink BWP from a set of configured downlinkBWPs may be linked with an uplink BWP from a set of configured uplinkBWPs if a downlink BWP index of the downlink BWP and an uplink BWP indexof the uplink BWP are the same. For unpaired spectra, a UE may expectthat a center frequency for a downlink BWP is the same as a centerfrequency for an uplink BWP.

For a downlink BWP in a set of configured downlink BWPs on a primarycell (PCell), a base station may configure a UE with one or more controlresource sets (CORESETs) for at least one search space. A search spaceis a set of locations in the time and frequency domains where the UE mayfind control information. The search space may be a UE-specific searchspace or a common search space (potentially usable by a plurality ofUEs). For example, a base station may configure a UE with a commonsearch space, on a PCell or on a primary secondary cell (PSCell), in anactive downlink BWP.

For an uplink BWP in a set of configured uplink BWPs, a BS may configurea UE with one or more resource sets for one or more PUCCH transmissions.A UE may receive downlink receptions (e.g., PDCCH or PDSCH) in adownlink BWP according to a configured numerology (e.g., subcarrierspacing and cyclic prefix duration) for the downlink BWP. The UE maytransmit uplink transmissions (e.g., PUCCH or PUSCH) in an uplink BWPaccording to a configured numerology (e.g., subcarrier spacing andcyclic prefix length for the uplink BWP).

One or more BWP indicator fields may be provided in Downlink ControlInformation (DCI). A value of a BWP indicator field may indicate whichBWP in a set of configured BWPs is an active downlink BWP for one ormore downlink receptions. The value of the one or more BWP indicatorfields may indicate an active uplink BWP for one or more uplinktransmissions.

A base station may semi-statically configure a UE with a defaultdownlink BWP within a set of configured downlink BWPs associated with aPCell. If the base station does not provide the default downlink BWP tothe UE, the default downlink BWP may be an initial active downlink BWP.The UE may determine which BWP is the initial active downlink BWP basedon a CORESET configuration obtained using the PBCH.

A base station may configure a UE with a BWP inactivity timer value fora PCell. The UE may start or restart a BWP inactivity timer at anyappropriate time. For example, the UE may start or restart the BWPinactivity timer (a) when the UE detects a DCI indicating an activedownlink BWP other than a default downlink BWP for a paired spectraoperation; or (b) when a UE detects a DCI indicating an active downlinkBWP or active uplink BWP other than a default downlink BWP or uplink BWPfor an unpaired spectra operation. If the UE does not detect DCI duringan interval of time (e.g., 1 ms or 0.5 ms), the UE may run the BWPinactivity timer toward expiration (for example, increment from zero tothe BWP inactivity timer value, or decrement from the BWP inactivitytimer value to zero). When the BWP inactivity timer expires, the UE mayswitch from the active downlink BWP to the default downlink BWP.

In an example, a base station may semi-statically configure a UE withone or more BWPs. A UE may switch an active BWP from a first BWP to asecond BWP in response to receiving a DCI indicating the second BWP asan active BWP and/or in response to an expiry of the BWP inactivitytimer (e.g., if the second BWP is the default BWP).

Downlink and uplink BWP switching (where BWP switching refers toswitching from a currently active BWP to a not currently active BWP) maybe performed independently in paired spectra. In unpaired spectra,downlink and uplink BWP switching may be performed simultaneously.Switching between configured BWPs may occur based on RRC signaling, DCI,expiration of a BWP inactivity timer, and/or an initiation of randomaccess.

FIG. 9 illustrates an example of bandwidth adaptation using threeconfigured BWPs for an NR carrier. A UE configured with the three BWPsmay switch from one BWP to another BWP at a switching point. In theexample illustrated in FIG. 9 , the BWPs include: a BWP 902 with abandwidth of 40 MHz and a subcarrier spacing of 15 kHz; a BWP 904 with abandwidth of 10 MHz and a subcarrier spacing of 15 kHz; and a BWP 906with a bandwidth of 20 MHz and a subcarrier spacing of 60 kHz. The BWP902 may be an initial active BWP, and the BWP 904 may be a default BWP.The UE may switch between BWPs at switching points. In the example ofFIG. 9 , the UE may switch from the BWP 902 to the BWP 904 at aswitching point 908. The switching at the switching point 908 may occurfor any suitable reason, for example, in response to an expiry of a BWPinactivity timer (indicating switching to the default BWP) and/or inresponse to receiving a DCI indicating BWP 904 as the active BWP. The UEmay switch at a switching point 910 from active BWP 904 to BWP 906 inresponse receiving a DCI indicating BWP 906 as the active BWP. The UEmay switch at a switching point 912 from active BWP 906 to BWP 904 inresponse to an expiry of a BWP inactivity timer and/or in responsereceiving a DCI indicating BWP 904 as the active BWP. The UE may switchat a switching point 914 from active BWP 904 to BWP 902 in responsereceiving a DCI indicating BWP 902 as the active BWP.

If a UE is configured for a secondary cell with a default downlink BWPin a set of configured downlink BWPs and a timer value, UE proceduresfor switching BWPs on a secondary cell may be the same/similar as thoseon a primary cell. For example, the UE may use the timer value and thedefault downlink BWP for the secondary cell in the same/similar manneras the UE would use these values for a primary cell.

To provide for greater data rates, two or more carriers can beaggregated and simultaneously transmitted to/from the same UE usingcarrier aggregation (CA). The aggregated carriers in CA may be referredto as component carriers (CCs). When CA is used, there are a number ofserving cells for the UE, one for a CC. The CCs may have threeconfigurations in the frequency domain.

FIG. 10A illustrates the three CA configurations with two CCs. In theintraband, contiguous configuration 1002, the two CCs are aggregated inthe same frequency band (frequency band A) and are located directlyadjacent to each other within the frequency band. In the intraband,non-contiguous configuration 1004, the two CCs are aggregated in thesame frequency band (frequency band A) and are separated in thefrequency band by a gap. In the interband configuration 1006, the twoCCs are located in frequency bands (frequency band A and frequency bandB).

In an example, up to 32 CCs may be aggregated. The aggregated CCs mayhave the same or different bandwidths, subcarrier spacing, and/orduplexing schemes (TDD or FDD). A serving cell for a UE using CA mayhave a downlink CC. For FDD, one or more uplink CCs may be optionallyconfigured for a serving cell. The ability to aggregate more downlinkcarriers than uplink carriers may be useful, for example, when the UEhas more data traffic in the downlink than in the uplink.

When CA is used, one of the aggregated cells for a UE may be referred toas a primary cell (PCell). The PCell may be the serving cell that the UEinitially connects to at RRC connection establishment, reestablishment,and/or handover. The PCell may provide the UE with NAS mobilityinformation and the security input. UEs may have different PCells. Inthe downlink, the carrier corresponding to the PCell may be referred toas the downlink primary CC (DL PCC). In the uplink, the carriercorresponding to the PCell may be referred to as the uplink primary CC(UL PCC). The other aggregated cells for the UE may be referred to assecondary cells (SCells). In an example, the SCells may be configuredafter the PCell is configured for the UE. For example, an SCell may beconfigured through an RRC Connection Reconfiguration procedure. In thedownlink, the carrier corresponding to an SCell may be referred to as adownlink secondary CC (DL SCC). In the uplink, the carrier correspondingto the SCell may be referred to as the uplink secondary CC (UL SCC).

Configured SCells for a UE may be activated and deactivated based on,for example, traffic and channel conditions. Deactivation of an SCellmay mean that PDCCH and PDSCH reception on the SCell is stopped andPUSCH, SRS, and CQI transmissions on the SCell are stopped. ConfiguredSCells may be activated and deactivated using a MAC CE with respect toFIG. 4B. For example, a MAC CE may use a bitmap (e.g., one bit perSCell) to indicate which SCells (e.g., in a subset of configured SCells)for the UE are activated or deactivated. Configured SCells may bedeactivated in response to an expiration of an SCell deactivation timer(e.g., one SCell deactivation timer per SCell).

Downlink control information, such as scheduling assignments andscheduling grants, for a cell may be transmitted on the cellcorresponding to the assignments and grants, which is known asself-scheduling. The DCI for the cell may be transmitted on anothercell, which is known as cross-carrier scheduling. Uplink controlinformation (e.g., HARQ acknowledgments and channel state feedback, suchas CQI, PMI, and/or RI) for aggregated cells may be transmitted on thePUCCH of the PCell. For a larger number of aggregated downlink CCs, thePUCCH of the PCell may become overloaded. Cells may be divided intomultiple PUCCH groups.

FIG. 10B illustrates an example of how aggregated cells may beconfigured into one or more PUCCH groups. A PUCCH group 1010 and a PUCCHgroup 1050 may include one or more downlink CCs, respectively. In theexample of FIG. 10B, the PUCCH group 1010 includes three downlink CCs: aPCell 1011, an SCell 1012, and an SCell 1013. The PUCCH group 1050includes three downlink CCs in the present example: a PCell 1051, anSCell 1052, and an SCell 1053. One or more uplink CCs may be configuredas a PCell 1021, an SCell 1022, and an SCell 1023. One or more otheruplink CCs may be configured as a primary SCell (PSCell) 1061, an SCell1062, and an SCell 1063. Uplink control information (UCI) related to thedownlink CCs of the PUCCH group 1010, shown as UCI 1031, UCI 1032, andUCI 1033, may be transmitted in the uplink of the PCell 1021. Uplinkcontrol information (UCI) related to the downlink CCs of the PUCCH group1050, shown as UCI 1071, UCI 1072, and UCI 1073, may be transmitted inthe uplink of the PSCell 1061. In an example, if the aggregated cellsdepicted in FIG. 10B were not divided into the PUCCH group 1010 and thePUCCH group 1050, a single uplink PCell to transmit UCI relating to thedownlink CCs, and the PCell may become overloaded. By dividingtransmissions of UCI between the PCell 1021 and the PSCell 1061,overloading may be prevented.

A cell, comprising a downlink carrier and optionally an uplink carrier,may be assigned with a physical cell ID and a cell index. The physicalcell ID or the cell index may identify a downlink carrier and/or anuplink carrier of the cell, for example, depending on the context inwhich the physical cell ID is used. A physical cell ID may be determinedusing a synchronization signal transmitted on a downlink componentcarrier. A cell index may be determined using RRC messages. In thedisclosure, a physical cell ID may be referred to as a carrier ID, and acell index may be referred to as a carrier index. For example, when thedisclosure refers to a first physical cell ID for a first downlinkcarrier, the disclosure may mean the first physical cell ID is for acell comprising the first downlink carrier. The same/similar concept mayapply to, for example, a carrier activation. When the disclosureindicates that a first carrier is activated, the specification may meanthat a cell comprising the first carrier is activated.

In CA, a multi-carrier nature of a PHY may be exposed to a MAC. In anexample, a HARQ entity may operate on a serving cell. A transport blockmay be generated per assignment/grant per serving cell. A transportblock and potential HARQ retransmissions of the transport block may bemapped to a serving cell.

In the downlink, a base station may transmit (e.g., unicast, multicast,and/or broadcast) one or more Reference Signals (RSs) to a UE (e.g.,PSS, SSS, CSI-RS, DMRS, and/or PT-RS, as shown in FIG. 5A). In theuplink, the UE may transmit one or more RSs to the base station (e.g.,DMRS, PT-RS, and/or SRS, as shown in FIG. 5B). The PSS and the SSS maybe transmitted by the base station and used by the UE to synchronize theUE to the base station. The PSS and the SSS may be provided in asynchronization signal (SS) / physical broadcast channel (PBCH) blockthat includes the PSS, the SSS, and the PBCH. The base station mayperiodically transmit a burst of SS/PBCH blocks.

FIG. 11A illustrates an example of an SS/PBCH block’s structure andlocation. A burst of SS/PBCH blocks may include one or more SS/PBCHblocks (e.g., 4 SS/PBCH blocks, as shown in FIG. 11A). Bursts may betransmitted periodically (e.g., every 2 frames or 20 ms). A burst may berestricted to a half-frame (e.g., a first half-frame having a durationof 5 ms). It will be understood that FIG. 11A is an example, and thatthese parameters (number of SS/PBCH blocks per burst, periodicity ofbursts, position of burst within the frame) may be configured based on,for example: a carrier frequency of a cell in which the SS/PBCH block istransmitted; a numerology or subcarrier spacing of the cell; aconfiguration by the network (e.g., using RRC signaling); or any othersuitable factor. In an example, the UE may assume a subcarrier spacingfor the SS/PBCH block based on the carrier frequency being monitored,unless the radio network configured the UE to assume a differentsubcarrier spacing.

The SS/PBCH block may span one or more OFDM symbols in the time domain(e.g., 4 OFDM symbols, as shown in the example of FIG. 11A) and may spanone or more subcarriers in the frequency domain (e.g., 240 contiguoussubcarriers). The PSS, the SSS, and the PBCH may have a common centerfrequency. The PSS may be transmitted first and may span, for example, 1OFDM symbol and 127 subcarriers. The SSS may be transmitted after thePSS (e.g., two symbols later) and may span 1 OFDM symbol and 127subcarriers. The PBCH may be transmitted after the PSS (e.g., across thenext 3 OFDM symbols) and may span 240 subcarriers.

The location of the SS/PBCH block in the time and frequency domains maynot be known to the UE (e.g., if the UE is searching for the cell). Tofind and select the cell, the UE may monitor a carrier for the PSS. Forexample, the UE may monitor a frequency location within the carrier. Ifthe PSS is not found after a certain duration (e.g., 20 ms), the UE maysearch for the PSS at a different frequency location within the carrier,as indicated by a synchronization raster. If the PSS is found at alocation in the time and frequency domains, the UE may determine, basedon a known structure of the SS/PBCH block, the locations of the SSS andthe PBCH, respectively. The SS/PBCH block may be a cell-defining SSblock (CD-SSB). In an example, a primary cell may be associated with aCD-SSB. The CD-SSB may be located on a synchronization raster. In anexample, a cell selection/search and/or reselection may be based on theCD-SSB.

The SS/PBCH block may be used by the UE to determine one or moreparameters of the cell. For example, the UE may determine a physicalcell identifier (PCI) of the cell based on the sequences of the PSS andthe SSS, respectively. The UE may determine a location of a frameboundary of the cell based on the location of the SS/PBCH block. Forexample, the SS/PBCH block may indicate that it has been transmitted inaccordance with a transmission pattern, wherein a SS/PBCH block in thetransmission pattern is a known distance from the frame boundary.

The PBCH may use a QPSK modulation and may use forward error correction(FEC). The FEC may use polar coding. One or more symbols spanned by thePBCH may carry one or more DMRSs for demodulation of the PBCH. The PBCHmay include an indication of a current system frame number (SFN) of thecell and/or a SS/PBCH block timing index. These parameters mayfacilitate time synchronization of the UE to the base station. The PBCHmay include a master information block (MIB) used to provide the UE withone or more parameters. The MIB may be used by the UE to locateremaining minimum system information (RMSI) associated with the cell.The RMSI may include a System Information Block Type 1 (SIB1). The SIB1may contain information needed by the UE to access the cell. The UE mayuse one or more parameters of the MIB to monitor PDCCH, which may beused to schedule PDSCH. The PDSCH may include the SIB1. The SIB1 may bedecoded using parameters provided in the MIB. The PBCH may indicate anabsence of SIB1. Based on the PBCH indicating the absence of SIB1, theUE may be pointed to a frequency. The UE may search for an SS/PBCH blockat the frequency to which the UE is pointed.

The UE may assume that one or more SS/PBCH blocks transmitted with asame SS/PBCH block index are quasi co-located (QCLed) (e.g., having thesame/similar Doppler spread, Doppler shift, average gain, average delay,and/or spatial Rx parameters). The UE may not assume QCL for SS/PBCHblock transmissions having different SS/PBCH block indices.

SS/PBCH blocks (e.g., those within a half-frame) may be transmitted inspatial directions (e.g., using different beams that span a coveragearea of the cell). In an example, a first SS/PBCH block may betransmitted in a first spatial direction using a first beam, and asecond SS/PBCH block may be transmitted in a second spatial directionusing a second beam.

In an example, within a frequency span of a carrier, a base station maytransmit a plurality of SS/PBCH blocks. In an example, a first PCI of afirst SS/PBCH block of the plurality of SS/PBCH blocks may be differentfrom a second PCI of a second SS/PBCH block of the plurality of SS/PBCHblocks. The PCIs of SS/PBCH blocks transmitted in different frequencylocations may be different or the same.

The CSI-RS may be transmitted by the base station and used by the UE toacquire channel state information (CSI). The base station may configurethe UE with one or more CSI-RSs for channel estimation or any othersuitable purpose. The base station may configure a UE with one or moreof the same/similar CSI-RSs. The UE may measure the one or more CSI-RSs.The UE may estimate a downlink channel state and/or generate a CSIreport based on the measuring of the one or more downlink CSI-RSs. TheUE may provide the CSI report to the base station. The base station mayuse feedback provided by the UE (e.g., the estimated downlink channelstate) to perform link adaptation.

The base station may semi-statically configure the UE with one or moreCSI-RS resource sets. A CSI-RS resource may be associated with alocation in the time and frequency domains and a periodicity. The basestation may selectively activate and/or deactivate a CSI-RS resource.The base station may indicate to the UE that a CSI-RS resource in theCSI-RS resource set is activated and/or deactivated.

The base station may configure the UE to report CSI measurements. Thebase station may configure the UE to provide CSI reports periodically,aperiodically, or semi-persistently. For periodic CSI reporting, the UEmay be configured with a timing and/or periodicity of a plurality of CSIreports. For aperiodic CSI reporting, the base station may request a CSIreport. For example, the base station may command the UE to measure aconfigured CSI-RS resource and provide a CSI report relating to themeasurements. For semi-persistent CSI reporting, the base station mayconfigure the UE to transmit periodically, and selectively activate ordeactivate the periodic reporting. The base station may configure the UEwith a CSI-RS resource set and CSI reports using RRC signaling.

The CSI-RS configuration may comprise one or more parameters indicating,for example, up to 32 antenna ports. The UE may be configured to employthe same OFDM symbols for a downlink CSI-RS and a control resource set(CORESET) when the downlink CSI-RS and CORESET are spatially QCLed andresource elements associated with the downlink CSI-RS are outside of thephysical resource blocks (PRBs) configured for the CORESET. The UE maybe configured to employ the same OFDM symbols for downlink CSI-RS andSS/PBCH blocks when the downlink CSI-RS and SS/PBCH blocks are spatiallyQCLed and resource elements associated with the downlink CSI-RS areoutside of PRBs configured for the SS/PBCH blocks.

Downlink DMRSs may be transmitted by a base station and used by a UE forchannel estimation. For example, the downlink DMRS may be used forcoherent demodulation of one or more downlink physical channels (e.g.,PDSCH). An NR network may support one or more variable and/orconfigurable DMRS patterns for data demodulation. At least one downlinkDMRS configuration may support a front-loaded DMRS pattern. Afront-loaded DMRS may be mapped over one or more OFDM symbols (e.g., oneor two adjacent OFDM symbols). A base station may semi-staticallyconfigure the UE with a number (e.g. a maximum number) of front-loadedDMRS symbols for PDSCH. A DMRS configuration may support one or moreDMRS ports. For example, for single user-MIMO, a DMRS configuration maysupport up to eight orthogonal downlink DMRS ports per UE. Formultiuser-MIMO, a DMRS configuration may support up to 4 orthogonaldownlink DMRS ports per UE. A radio network may support (e.g., at leastfor CP-OFDM) a common DMRS structure for downlink and uplink, wherein aDMRS location, a DMRS pattern, and/or a scrambling sequence may be thesame or different. The base station may transmit a downlink DMRS and acorresponding PDSCH using the same precoding matrix. The UE may use theone or more downlink DMRSs for coherent demodulation/channel estimationof the PDSCH.

In an example, a transmitter (e.g., a base station) may use a precodermatrices for a part of a transmission bandwidth. For example, thetransmitter may use a first precoder matrix for a first bandwidth and asecond precoder matrix for a second bandwidth. The first precoder matrixand the second precoder matrix may be different based on the firstbandwidth being different from the second bandwidth. The UE may assumethat a same precoding matrix is used across a set of PRBs. The set ofPRBs may be denoted as a precoding resource block group (PRG).

A PDSCH may comprise one or more layers. The UE may assume that at leastone symbol with DMRS is present on a layer of the one or more layers ofthe PDSCH. A higher layer may configure up to 3 DMRSs for the PDSCH.

Downlink PT-RS may be transmitted by a base station and used by a UE forphase-noise compensation. Whether a downlink PT-RS is present or not maydepend on an RRC configuration. The presence and/or pattern of thedownlink PT-RS may be configured on a UE-specific basis using acombination of RRC signaling and/or an association with one or moreparameters employed for other purposes (e.g., modulation and codingscheme (MCS)), which may be indicated by DCI. When configured, a dynamicpresence of a downlink PT-RS may be associated with one or more DCIparameters comprising at least MCS. An NR network may support aplurality of PT-RS densities defined in the time and/or frequencydomains. When present, a frequency domain density may be associated withat least one configuration of a scheduled bandwidth. The UE may assume asame precoding for a DMRS port and a PT-RS port. A number of PT-RS portsmay be fewer than a number of DMRS ports in a scheduled resource.Downlink PT-RS may be confined in the scheduled time/frequency durationfor the UE. Downlink PT-RS may be transmitted on symbols to facilitatephase tracking at the receiver.

The UE may transmit an uplink DMRS to a base station for channelestimation. For example, the base station may use the uplink DMRS forcoherent demodulation of one or more uplink physical channels. Forexample, the UE may transmit an uplink DMRS with a PUSCH and/or a PUCCH.The uplink DM-RS may span a range of frequencies that is similar to arange of frequencies associated with the corresponding physical channel.The base station may configure the UE with one or more uplink DMRSconfigurations. At least one DMRS configuration may support afront-loaded DMRS pattern. The front-loaded DMRS may be mapped over oneor more OFDM symbols (e.g., one or two adjacent OFDM symbols). One ormore uplink DMRSs may be configured to transmit at one or more symbolsof a PUSCH and/or a PUCCH. The base station may semi-staticallyconfigure the UE with a number (e.g. maximum number) of front-loadedDMRS symbols for the PUSCH and/or the PUCCH, which the UE may use toschedule a single-symbol DMRS and/or a double-symbol DMRS. An NR networkmay support (e.g., for cyclic prefix orthogonal frequency divisionmultiplexing (CP-OFDM)) a common DMRS structure for downlink and uplink,wherein a DMRS location, a DMRS pattern, and/or a scrambling sequencefor the DMRS may be the same or different.

A PUSCH may comprise one or more layers, and the UE may transmit atleast one symbol with DMRS present on a layer of the one or more layersof the PUSCH. In an example, a higher layer may configure up to threeDMRSs for the PUSCH.

Uplink PT-RS (which may be used by a base station for phase trackingand/or phase-noise compensation) may or may not be present depending onan RRC configuration of the UE. The presence and/or pattern of uplinkPT-RS may be configured on a UE-specific basis by a combination of RRCsignaling and/or one or more parameters employed for other purposes(e.g., Modulation and Coding Scheme (MCS)), which may be indicated byDCI. When configured, a dynamic presence of uplink PT-RS may beassociated with one or more DCI parameters comprising at least MCS. Aradio network may support a plurality of uplink PT-RS densities definedin time/frequency domain. When present, a frequency domain density maybe associated with at least one configuration of a scheduled bandwidth.The UE may assume a same precoding for a DMRS port and a PT-RS port. Anumber of PT-RS ports may be fewer than a number of DMRS ports in ascheduled resource. For example, uplink PT-RS may be confined in thescheduled time/frequency duration for the UE.

SRS may be transmitted by a UE to a base station for channel stateestimation to support uplink channel dependent scheduling and/or linkadaptation. SRS transmitted by the UE may allow a base station toestimate an uplink channel state at one or more frequencies. A schedulerat the base station may employ the estimated uplink channel state toassign one or more resource blocks for an uplink PUSCH transmission fromthe UE. The base station may semi-statically configure the UE with oneor more SRS resource sets. For an SRS resource set, the base station mayconfigure the UE with one or more SRS resources. An SRS resource setapplicability may be configured by a higher layer (e.g., RRC) parameter.For example, when a higher layer parameter indicates beam management, anSRS resource in a SRS resource set of the one or more SRS resource sets(e.g., with the same/similar time domain behavior, periodic, aperiodic,and/or the like) may be transmitted at a time instant (e.g.,simultaneously). The UE may transmit one or more SRS resources in SRSresource sets. An NR network may support aperiodic, periodic and/orsemi-persistent SRS transmissions. The UE may transmit SRS resourcesbased on one or more trigger types, wherein the one or more triggertypes may comprise higher layer signaling (e.g., RRC) and/or one or moreDCI formats. In an example, at least one DCI format may be employed forthe UE to select at least one of one or more configured SRS resourcesets. An SRS trigger type 0 may refer to an SRS triggered based on ahigher layer signaling. An SRS trigger type 1 may refer to an SRStriggered based on one or more DCI formats. In an example, when PUSCHand SRS are transmitted in a same slot, the UE may be configured totransmit SRS after a transmission of a PUSCH and a corresponding uplinkDMRS.

The base station may semi-statically configure the UE with one or moreSRS configuration parameters indicating at least one of following: a SRSresource configuration identifier; a number of SRS ports; time domainbehavior of an SRS resource configuration (e.g., an indication ofperiodic, semi-persistent, or aperiodic SRS); slot, mini-slot, and/orsubframe level periodicity; offset for a periodic and/or an aperiodicSRS resource; a number of OFDM symbols in an SRS resource; a startingOFDM symbol of an SRS resource; an SRS bandwidth; a frequency hoppingbandwidth; a cyclic shift; and/or an SRS sequence ID.

An antenna port is defined such that the channel over which a symbol onthe antenna port is conveyed can be inferred from the channel over whichanother symbol on the same antenna port is conveyed. If a first symboland a second symbol are transmitted on the same antenna port, thereceiver may infer the channel (e.g., fading gain, multipath delay,and/or the like) for conveying the second symbol on the antenna port,from the channel for conveying the first symbol on the antenna port. Afirst antenna port and a second antenna port may be referred to as quasico-located (QCLed) if one or more large-scale properties of the channelover which a first symbol on the first antenna port is conveyed may beinferred from the channel over which a second symbol on a second antennaport is conveyed. The one or more large-scale properties may comprise atleast one of: a delay spread; a Doppler spread; a Doppler shift; anaverage gain; an average delay; and/or spatial Receiving (Rx)parameters.

Channels that use beamforming require beam management. Beam managementmay comprise beam measurement, beam selection, and beam indication. Abeam may be associated with one or more reference signals. For example,a beam may be identified by one or more beamformed reference signals.The UE may perform downlink beam measurement based on downlink referencesignals (e.g., a channel state information reference signal (CSI-RS))and generate a beam measurement report. The UE may perform the downlinkbeam measurement procedure after an RRC connection is set up with a basestation.

FIG. 11B illustrates an example of channel state information referencesignals (CSI-RSs) that are mapped in the time and frequency domains. Asquare shown in FIG. 11B may span a resource block (RB) within abandwidth of a cell. A base station may transmit one or more RRCmessages comprising CSI-RS resource configuration parameters indicatingone or more CSI-RSs. One or more of the following parameters may beconfigured by higher layer signaling (e.g., RRC and/or MAC signaling)for a CSI-RS resource configuration: a CSI-RS resource configurationidentity, a number of CSI-RS ports, a CSI-RS configuration (e.g., symboland resource element (RE) locations in a subframe), a CSI-RS subframeconfiguration (e.g., subframe location, offset, and periodicity in aradio frame), a CSI-RS power parameter, a CSI-RS sequence parameter, acode division multiplexing (CDM) type parameter, a frequency density, atransmission comb, quasi co-location (QCL) parameters (e.g.,QCL-scramblingidentity, crs-portscount, mbsfn-subframeconfiglist,csi-rs-configZPid, qcl-csi-rs-configNZPid), and/or other radio resourceparameters.

The three beams illustrated in FIG. 11B may be configured for a UE in aUE-specific configuration. Three beams are illustrated in FIG. 11B (beam#1, beam #2, and beam #3), more or fewer beams may be configured. Beam#1 may be allocated with CSI-RS 1101 that may be transmitted in one ormore subcarriers in an RB of a first symbol. Beam #2 may be allocatedwith CSI-RS 1102 that may be transmitted in one or more subcarriers inan RB of a second symbol. Beam #3 may be allocated with CSI-RS 1103 thatmay be transmitted in one or more subcarriers in an RB of a thirdsymbol. By using frequency division multiplexing (FDM), a base stationmay use other subcarriers in a same RB (for example, those that are notused to transmit CSI-RS 1101) to transmit another CSI-RS associated witha beam for another UE. By using time domain multiplexing (TDM), beamsused for the UE may be configured such that beams for the UE use symbolsfrom beams of other UEs.

CSI-RSs such as those illustrated in FIG. 11B (e.g., CSI-RS 1101, 1102,1103) may be transmitted by the base station and used by the UE for oneor more measurements. For example, the UE may measure a reference signalreceived power (RSRP) of configured CSI-RS resources. The base stationmay configure the UE with a reporting configuration and the UE mayreport the RSRP measurements to a network (for example, via one or morebase stations) based on the reporting configuration. In an example, thebase station may determine, based on the reported measurement results,one or more transmission configuration indication (TCI) statescomprising a number of reference signals. In an example, the basestation may indicate one or more TCI states to the UE (e.g., via RRCsignaling, a MAC CE, and/or a DCI). The UE may receive a downlinktransmission with a receive (Rx) beam determined based on the one ormore TCI states. In an example, the UE may or may not have a capabilityof beam correspondence. If the UE has the capability of beamcorrespondence, the UE may determine a spatial domain filter of atransmit (Tx) beam based on a spatial domain filter of the correspondingRx beam. If the UE does not have the capability of beam correspondence,the UE may perform an uplink beam selection procedure to determine thespatial domain filter of the Tx beam. The UE may perform the uplink beamselection procedure based on one or more sounding reference signal (SRS)resources configured to the UE by the base station. The base station mayselect and indicate uplink beams for the UE based on measurements of theone or more SRS resources transmitted by the UE.

In a beam management procedure, a UE may assess (e.g., measure) achannel quality of one or more beam pair links, a beam pair linkcomprising a transmitting beam transmitted by a base station and areceiving beam received by the UE. Based on the assessment, the UE maytransmit a beam measurement report indicating one or more beam pairquality parameters comprising, e.g., one or more beam identifications(e.g., a beam index, a reference signal index, or the like), RSRP, aprecoding matrix indicator (PMI), a channel quality indicator (CQI),and/or a rank indicator (RI).

FIG. 12A illustrates examples of three downlink beam managementprocedures: P1, P2, and P3. Procedure P1 may enable a UE measurement ontransmit (Tx) beams of a transmission reception point (TRP) (or multipleTRPs), e.g., to support a selection of one or more base station Tx beamsand/or UE Rx beams (shown as ovals in the top row and bottom row,respectively, of P1). Beamforming at a TRP may comprise a Tx beam sweepfor a set of beams (shown, in the top rows of P1 and P2, as ovalsrotated in a counter-clockwise direction indicated by the dashed arrow).Beamforming at a UE may comprise an Rx beam sweep for a set of beams(shown, in the bottom rows of P1 and P3, as ovals rotated in a clockwisedirection indicated by the dashed arrow). Procedure P2 may be used toenable a UE measurement on Tx beams of a TRP (shown, in the top row ofP2, as ovals rotated in a counter-clockwise direction indicated by thedashed arrow). The UE and/or the base station may perform procedure P2using a smaller set of beams than is used in procedure P1, or usingnarrower beams than the beams used in procedure P1. This may be referredto as beam refinement. The UE may perform procedure P3 for Rx beamdetermination by using the same Tx beam at the base station and sweepingan Rx beam at the UE.

FIG. 12B illustrates examples of three uplink beam managementprocedures: U1, U2, and U3. Procedure U1 may be used to enable a basestation to perform a measurement on Tx beams of a UE, e.g., to support aselection of one or more UE Tx beams and/or base station Rx beams (shownas ovals in the top row and bottom row, respectively, of U1).Beamforming at the UE may include, e.g., a Tx beam sweep from a set ofbeams (shown in the bottom rows of U1 and U3 as ovals rotated in aclockwise direction indicated by the dashed arrow). Beamforming at thebase station may include, e.g., an Rx beam sweep from a set of beams(shown, in the top rows of U1 and U2, as ovals rotated in acounter-clockwise direction indicated by the dashed arrow). Procedure U2may be used to enable the base station to adjust its Rx beam when the UEuses a fixed Tx beam. The UE and/or the base station may performprocedure U2 using a smaller set of beams than is used in procedure P1,or using narrower beams than the beams used in procedure P1. This may bereferred to as beam refinement The UE may perform procedure U3 to adjustits Tx beam when the base station uses a fixed Rx beam.

A UE may initiate a beam failure recovery (BFR) procedure based ondetecting a beam failure. The UE may transmit a BFR request (e.g., apreamble, a UCI, an SR, a MAC CE, and/or the like) based on theinitiating of the BFR procedure. The UE may detect the beam failurebased on a determination that a quality of beam pair link(s) of anassociated control channel is unsatisfactory (e.g., having an error ratehigher than an error rate threshold, a received signal power lower thana received signal power threshold, an expiration of a timer, and/or thelike).

The UE may measure a quality of a beam pair link using one or morereference signals (RSs) comprising one or more SS/PBCH blocks, one ormore CSI-RS resources, and/or one or more demodulation reference signals(DMRSs). A quality of the beam pair link may be based on one or more ofa block error rate (BLER), an RSRP value, a signal to interference plusnoise ratio (SINR) value, a reference signal received quality (RSRQ)value, and/or a CSI value measured on RS resources. The base station mayindicate that an RS resource is quasi co-located (QCLed) with one ormore DM-RSs of a channel (e.g., a control channel, a shared datachannel, and/or the like). The RS resource and the one or more DMRSs ofthe channel may be QCLed when the channel characteristics (e.g., Dopplershift, Doppler spread, average delay, delay spread, spatial Rxparameter, fading, and/or the like) from a transmission via the RSresource to the UE are similar or the same as the channelcharacteristics from a transmission via the channel to the UE.

A network (e.g., a gNB and/or an ng-eNB of a network) and/or the UE mayinitiate a random access procedure. A UE in an RRC_IDLE state and/or anRRC_INACTIVE state may initiate the random access procedure to request aconnection setup to a network. The UE may initiate the random accessprocedure from an RRC_CONNECTED state. The UE may initiate the randomaccess procedure to request uplink resources (e.g., for uplinktransmission of an SR when there is no PUCCH resource available) and/oracquire uplink timing (e.g., when uplink synchronization status isnon-synchronized). The UE may initiate the random access procedure torequest one or more system information blocks (SIBs) (e.g., other systeminformation such as SIB2, SIB3, and/or the like). The UE may initiatethe random access procedure for a beam failure recovery request. Anetwork may initiate a random access procedure for a handover and/or forestablishing time alignment for an SCell addition.

FIG. 13A illustrates a four-step contention-based random accessprocedure. Prior to initiation of the procedure, a base station maytransmit a configuration message 1310 to the UE. The procedureillustrated in FIG. 13A comprises transmission of four messages: a Msg 11311, a Msg 2 1312, a Msg 3 1313, and a Msg 4 1314. The Msg 1 1311 mayinclude and/or be referred to as a preamble (or a random accesspreamble). The Msg 2 1312 may include and/or be referred to as a randomaccess response (RAR).

The configuration message 1310 may be transmitted, for example, usingone or more RRC messages. The one or more RRC messages may indicate oneor more random access channel (RACH) parameters to the UE. The one ormore RACH parameters may comprise at least one of following: generalparameters for one or more random access procedures (e.g.,RACH-configGeneral); cell-specific parameters (e.g., RACH-ConfigCommon);and/or dedicated parameters (e.g., RACH-configDedicated). The basestation may broadcast or multicast the one or more RRC messages to oneor more UEs. The one or more RRC messages may be UE-specific (e.g.,dedicated RRC messages transmitted to a UE in an RRC_CONNECTED stateand/or in an RRC_INACTIVE state). The UE may determine, based on the oneor more RACH parameters, a time-frequency resource and/or an uplinktransmit power for transmission of the Msg 1 1311 and/or the Msg 3 1313.Based on the one or more RACH parameters, the UE may determine areception timing and a downlink channel for receiving the Msg 2 1312 andthe Msg 4 1314.

The one or more RACH parameters provided in the configuration message1310 may indicate one or more Physical RACH (PRACH) occasions availablefor transmission of the Msg 1 1311. The one or more PRACH occasions maybe predefined. The one or more RACH parameters may indicate one or moreavailable sets of one or more PRACH occasions (e.g., prach-Configlndex).The one or more RACH parameters may indicate an association between (a)one or more PRACH occasions and (b) one or more reference signals. Theone or more RACH parameters may indicate an association between (a) oneor more preambles and (b) one or more reference signals. The one or morereference signals may be SS/PBCH blocks and/or CSI-RSs. For example, theone or more RACH parameters may indicate a number of SS/PBCH blocksmapped to a PRACH occasion and/or a number of preambles mapped to aSS/PBCH blocks.

The one or more RACH parameters provided in the configuration message1310 may be used to determine an uplink transmit power of Msg 1 1311and/or Msg 3 1313. For example, the one or more RACH parameters mayindicate a reference power for a preamble transmission (e.g., a receivedtarget power and/or an initial power of the preamble transmission).There may be one or more power offsets indicated by the one or more RACHparameters. For example, the one or more RACH parameters may indicate: apower ramping step; a power offset between SSB and CSI-RS; a poweroffset between transmissions of the Msg 1 1311 and the Msg 3 1313;and/or a power offset value between preamble groups. The one or moreRACH parameters may indicate one or more thresholds based on which theUE may determine at least one reference signal (e.g., an SSB and/orCSI-RS) and/or an uplink carrier (e.g., a normal uplink (NUL) carrierand/or a supplemental uplink (SUL) carrier).

The Msg 1 1311 may include one or more preamble transmissions (e.g., apreamble transmission and one or more preamble retransmissions). An RRCmessage may be used to configure one or more preamble groups (e.g.,group A and/or group B). A preamble group may comprise one or morepreambles. The UE may determine the preamble group based on a pathlossmeasurement and/or a size of the Msg 3 1313. The UE may measure an RSRPof one or more reference signals (e.g., SSBs and/or CSI-RSs) anddetermine at least one reference signal having an RSRP above an RSRPthreshold (e.g., rsrp-ThresholdSSB and/or rsrp-ThresholdCSI-RS). The UEmay select at least one preamble associated with the one or morereference signals and/or a selected preamble group, for example, if theassociation between the one or more preambles and the at least onereference signal is configured by an RRC message.

The UE may determine the preamble based on the one or more RACHparameters provided in the configuration message 1310. For example, theUE may determine the preamble based on a pathloss measurement, an RSRPmeasurement, and/or a size of the Msg 3 1313. As another example, theone or more RACH parameters may indicate: a preamble format; a maximumnumber of preamble transmissions; and/or one or more thresholds fordetermining one or more preamble groups (e.g., group A and group B). Abase station may use the one or more RACH parameters to configure the UEwith an association between one or more preambles and one or morereference signals (e.g., SSBs and/or CSI-RSs). If the association isconfigured, the UE may determine the preamble to include in Msg 1 1311based on the association. The Msg 1 1311 may be transmitted to the basestation via one or more PRACH occasions. The UE may use one or morereference signals (e.g., SSBs and/or CSI-RSs) for selection of thepreamble and for determining of the PRACH occasion. One or more RACHparameters (e.g., ra-ssb-OccasionMsklndex and/or ra-OccasionList) mayindicate an association between the PRACH occasions and the one or morereference signals.

The UE may perform a preamble retransmission if no response is receivedfollowing a preamble transmission. The UE may increase an uplinktransmit power for the preamble retransmission. The UE may select aninitial preamble transmit power based on a pathloss measurement and/or atarget received preamble power configured by the network. The UE maydetermine to retransmit a preamble and may ramp up the uplink transmitpower. The UE may receive one or more RACH parameters (e.g.,PREAMBLE_POWER_RAMPING_STEP) indicating a ramping step for the preambleretransmission. The ramping step may be an amount of incrementalincrease in uplink transmit power for a retransmission. The UE may rampup the uplink transmit power if the UE determines a reference signal(e.g., SSB and/or CSI-RS) that is the same as a previous preambletransmission. The UE may count a number of preamble transmissions and/orretransmissions (e.g., PREAMBLE­_TRANSMISSION_COUNTER). The UE maydetermine that a random access procedure completed unsuccessfully, forexample, if the number of preamble transmissions exceeds a thresholdconfigured by the one or more RACH parameters (e.g., preambleTransMax).

The Msg 2 1312 received by the UE may include an RAR. In some scenarios,the Msg 2 1312 may include multiple RARs corresponding to multiple UEs.The Msg 2 1312 may be received after or in response to the transmittingof the Msg 1 1311. The Msg 2 1312 may be scheduled on the DL-SCH andindicated on a PDCCH using a random access RNTI (RA-RNTI). The Msg 21312 may indicate that the Msg 1 1311 was received by the base station.The Msg 2 1312 may include a time-alignment command that may be used bythe UE to adjust the UE’s transmission timing, a scheduling grant fortransmission of the Msg 3 1313, and/or a Temporary Cell RNTI (TC-RNTI).After transmitting a preamble, the UE may start a time window (e.g.,ra-ResponseWindow) to monitor a PDCCH for the Msg 2 1312. The UE maydetermine when to start the time window based on a PRACH occasion thatthe UE uses to transmit the preamble. For example, the UE may start thetime window one or more symbols after a last symbol of the preamble(e.g., at a first PDCCH occasion from an end of a preambletransmission). The one or more symbols may be determined based on anumerology. The PDCCH may be in a common search space (e.g., aType1-PDCCH common search space) configured by an RRC message. The UEmay identify the RAR based on a Radio Network Temporary Identifier(RNTI). RNTIs may be used depending on one or more events initiating therandom access procedure. The UE may use random access RNTI (RA-RNTI).The RA-RNTI may be associated with PRACH occasions in which the UEtransmits a preamble. For example, the UE may determine the RA-RNTIbased on: an OFDM symbol index; a slot index; a frequency domain index;and/or a UL carrier indicator of the PRACH occasions. An example ofRA-RNTI may be as follows:

RA-RNTI= 1 + s_id + 14 × t_id + 14 × 80 × f_id + 14 × 80 × 8 × ul_carrier_id

where s_id may be an index of a first OFDM symbol of the PRACH occasion(e.g., 0 ≤ s_id < 14), t_id may be an index of a first slot of the PRACHoccasion in a system frame (e.g., 0 ≤ t_id < 80), f_id may be an indexof the PRACH occasion in the frequency domain (e.g., 0 ≤ f_id < 8), andul_carrier_id may be a UL carrier used for a preamble transmission(e.g., 0 for an NUL carrier, and 1 for an SUL carrier).

The UE may transmit the Msg 3 1313 in response to a successful receptionof the Msg 2 1312 (e.g., using resources identified in the Msg 2 1312).The Msg 3 1313 may be used for contention resolution in, for example,the contention-based random access procedure illustrated in FIG. 13A. Insome scenarios, a plurality of UEs may transmit a same preamble to abase station and the base station may provide an RAR that corresponds toa UE. Collisions may occur if the plurality of UEs interpret the RAR ascorresponding to themselves. Contention resolution (e.g., using the Msg3 1313 and the Msg 4 1314) may be used to increase the likelihood thatthe UE does not incorrectly use an identity of another the UE. Toperform contention resolution, the UE may include a device identifier inthe Msg 3 1313 (e.g., a C-RNTI if assigned, a TC-RNTI included in theMsg 2 1312, and/or any other suitable identifier).

The Msg 4 1314 may be received after or in response to the transmittingof the Msg 3 1313. If a C-RNTI was included in the Msg 3 1313, the basestation will address the UE on the PDCCH using the C-RNTI. If the UE’sunique C-RNTI is detected on the PDCCH, the random access procedure isdetermined to be successfully completed. If a TC-RNTI is included in theMsg 3 1313 (e.g., if the UE is in an RRC_IDLE state or not otherwiseconnected to the base station), Msg 4 1314 will be received using aDL-SCH associated with the TC-RNTI. If a MAC PDU is successfully decodedand a MAC PDU comprises the UE contention resolution identity MAC CEthat matches or otherwise corresponds with the CCCH SDU sent (e.g.,transmitted) in Msg 3 1313, the UE may determine that the contentionresolution is successful and/or the UE may determine that the randomaccess procedure is successfully completed.

The UE may be configured with a supplementary uplink (SUL) carrier and anormal uplink (NUL) carrier. An initial access (e.g., random accessprocedure) may be supported in an uplink carrier. For example, a basestation may configure the UE with two separate RACH configurations: onefor an SUL carrier and the other for an NUL carrier. For random accessin a cell configured with an SUL carrier, the network may indicate whichcarrier to use (NUL or SUL). The UE may determine the SUL carrier, forexample, if a measured quality of one or more reference signals is lowerthan a broadcast threshold. Uplink transmissions of the random accessprocedure (e.g., the Msg 1 1311 and/or the Msg 3 1313) may remain on theselected carrier. The UE may switch an uplink carrier during the randomaccess procedure (e.g., between the Msg 1 1311 and the Msg 3 1313) inone or more cases. For example, the UE may determine and/or switch anuplink carrier for the Msg 1 1311 and/or the Msg 3 1313 based on achannel clear assessment (e.g., a listen-before-talk).

FIG. 13B illustrates a two-step contention-free random access procedure.Similar to the four-step contention-based random access procedureillustrated in FIG. 13A, a base station may, prior to initiation of theprocedure, transmit a configuration message 1320 to the UE. Theconfiguration message 1320 may be analogous in some respects to theconfiguration message 1310. The procedure illustrated in FIG. 13Bcomprises transmission of two messages: a Msg 1 1321 and a Msg 2 1322.The Msg 1 1321 and the Msg 2 1322 may be analogous in some respects tothe Msg 1 1311 and a Msg 2 1312 illustrated in FIG. 13A, respectively.As will be understood from FIGS. 13A and 13B, the contention-free randomaccess procedure may not include messages analogous to the Msg 3 1313and/or the Msg 4 1314.

The contention-free random access procedure illustrated in FIG. 13B maybe initiated for a beam failure recovery, other SI request, SCelladdition, and/or handover. For example, a base station may indicate orassign to the UE the preamble to be used for the Msg 1 1321. The UE mayreceive, from the base station via PDCCH and/or RRC, an indication of apreamble (e.g., ra-Preamblelndex).

After transmitting a preamble, the UE may start a time window (e.g.,ra-ResponseWindow) to monitor a PDCCH for the RAR. In the event of abeam failure recovery request, the base station may configure the UEwith a separate time window and/or a separate PDCCH in a search spaceindicated by an RRC message (e.g., recoverySearchSpaceld). The UE maymonitor for a PDCCH transmission addressed to a Cell RNTI (C-RNTI) onthe search space. In the contention-free random access procedureillustrated in FIG. 13B, the UE may determine that a random accessprocedure successfully completes after or in response to transmission ofMsg 1 1321 and reception of a corresponding Msg 2 1322. The UE maydetermine that a random access procedure successfully completes, forexample, if a PDCCH transmission is addressed to a C-RNTI. The UE maydetermine that a random access procedure successfully completes, forexample, if the UE receives an RAR comprising a preamble identifiercorresponding to a preamble transmitted by the UE and/or the RARcomprises a MAC sub-PDU with the preamble identifier. The UE maydetermine the response as an indication of an acknowledgement for an SIrequest.

FIG. 13C illustrates another two-step random access procedure. Similarto the random access procedures illustrated in FIGS. 13A and 13B, a basestation may, prior to initiation of the procedure, transmit aconfiguration message 1330 to the UE. The configuration message 1330 maybe analogous in some respects to the configuration message 1310 and/orthe configuration message 1320. The procedure illustrated in FIG. 13Ccomprises transmission of two messages: a Msg A 1331 and a Msg B 1332.

Msg A 1331 may be transmitted in an uplink transmission by the UE. Msg A1331 may comprise one or more transmissions of a preamble 1341 and/orone or more transmissions of a transport block 1342. The transport block1342 may comprise contents that are similar and/or equivalent to thecontents of the Msg 3 1313 illustrated in FIG. 13A. The transport block1342 may comprise UCI (e.g., an SR, a HARQ ACK/NACK, and/or the like).The UE may receive the Msg B 1332 after or in response to transmittingthe Msg A 1331. The Msg B 1332 may comprise contents that are similarand/or equivalent to the contents of the Msg 2 1312 (e.g., an RAR)illustrated in FIGS. 13A and 13B and/or the Msg 4 1314 illustrated inFIG. 13A.

The UE may initiate the two-step random access procedure in FIG. 13C forlicensed spectrum and/or unlicensed spectrum. The UE may determine,based on one or more factors, whether to initiate the two-step randomaccess procedure. The one or more factors may be: a radio accesstechnology in use (e.g., LTE, NR, and/or the like); whether the UE hasvalid TA or not; a cell size; the UE’s RRC state; a type of spectrum(e.g., licensed vs. unlicensed); and/or any other suitable factors.

The UE may determine, based on two-step RACH parameters included in theconfiguration message 1330, a radio resource and/or an uplink transmitpower for the preamble 1341 and/or the transport block 1342 included inthe Msg A 1331. The RACH parameters may indicate a modulation and codingschemes (MCS), a time-frequency resource, and/or a power control for thepreamble 1341 and/or the transport block 1342. A time-frequency resourcefor transmission of the preamble 1341 (e.g., a PRACH) and atime-frequency resource for transmission of the transport block 1342(e.g., a PUSCH) may be multiplexed using FDM, TDM, and/or CDM. The RACHparameters may enable the UE to determine a reception timing and adownlink channel for monitoring for and/or receiving Msg B 1332.

The transport block 1342 may comprise data (e.g., delay-sensitive data),an identifier of the UE, security information, and/or device information(e.g., an International Mobile Subscriber Identity (IMSI)). The basestation may transmit the Msg B 1332 as a response to the Msg A 1331. TheMsg B 1332 may comprise at least one of following: a preambleidentifier; a timing advance command; a power control command; an uplinkgrant (e.g., a radio resource assignment and/or an MCS); a UE identifierfor contention resolution; and/or an RNTI (e.g., a C-RNTI or a TC-RNTI).The UE may determine that the two-step random access procedure issuccessfully completed if: a preamble identifier in the Msg B 1332 ismatched to a preamble transmitted by the UE; and/or the identifier ofthe UE in Msg B 1332 is matched to the identifier of the UE in the Msg A1331 (e.g., the transport block 1342).

A UE and a base station may exchange control signaling. The controlsignaling may be referred to as L1/L2 control signaling and mayoriginate from the PHY layer (e.g., layer 1) and/or the MAC layer (e.g.,layer 2). The control signaling may comprise downlink control signalingtransmitted from the base station to the UE and/or uplink controlsignaling transmitted from the UE to the base station.

The downlink control signaling may comprise: a downlink schedulingassignment; an uplink scheduling grant indicating uplink radio resourcesand/or a transport format; a slot format information; a preemptionindication; a power control command; and/or any other suitablesignaling. The UE may receive the downlink control signaling in apayload transmitted by the base station on a physical downlink controlchannel (PDCCH). The payload transmitted on the PDCCH may be referred toas downlink control information (DCI). In some scenarios, the PDCCH maybe a group common PDCCH (GC-PDCCH) that is common to a group of UEs.

A base station may attach one or more cyclic redundancy check (CRC)parity bits to a DCI in order to facilitate detection of transmissionerrors. When the DCI is intended for a UE (or a group of the UEs), thebase station may scramble the CRC parity bits with an identifier of theUE (or an identifier of the group of the UEs). Scrambling the CRC paritybits with the identifier may comprise Modulo-2 addition (or an exclusiveOR operation) of the identifier value and the CRC parity bits. Theidentifier may comprise a 16-bit value of a radio network temporaryidentifier (RNTI).

DCIs may be used for different purposes. A purpose may be indicated bythe type of RNTI used to scramble the CRC parity bits. For example, aDCI having CRC parity bits scrambled with a paging RNTI (P-RNTI) mayindicate paging information and/or a system information changenotification. The P-RNTI may be predefined as “FFFE” in hexadecimal. ADCI having CRC parity bits scrambled with a system information RNTI(SI-RNTI) may indicate a broadcast transmission of the systeminformation. The SI-RNTI may be predefined as “FFFF” in hexadecimal. ADCI having CRC parity bits scrambled with a random access RNTI (RA-RNTI)may indicate a random access response (RAR). A DCI having CRC paritybits scrambled with a cell RNTI (C-RNTI) may indicate a dynamicallyscheduled unicast transmission and/or a triggering of PDCCH-orderedrandom access. A DCI having CRC parity bits scrambled with a temporarycell RNTI (TC-RNTI) may indicate a contention resolution (e.g., a Msg 3analogous to the Msg 3 1313 illustrated in FIG. 13A). Other RNTIsconfigured to the UE by a base station may comprise a ConfiguredScheduling RNTI (CS-RNTI), a Transmit Power Control-PUCCH RNTI(TPC-PUCCH-RNTI), a Transmit Power Control-PUSCH RNTI (TPC-PUSCH-RNTI),a Transmit Power Control-SRS RNTI (TPC-SRS-RNTI), an Interruption RNTI(INT-RNTI), a Slot Format Indication RNTI (SFI-RNTI), a Semi-PersistentCSI RNTI (SP-CSI-RNTI), a Modulation and Coding Scheme Cell RNTI(MCS-C-RNTI), and/or the like.

Depending on the purpose and/or content of a DCI, the base station maytransmit the DCIs with one or more DCI formats. For example, DCI format0_0 may be used for scheduling of PUSCH in a cell. DCI format 0_0 may bea fallback DCI format (e.g., with compact DCI payloads). DCI format 0_1may be used for scheduling of PUSCH in a cell (e.g., with more DCIpayloads than DCI format 0_0). DCI format 1_0 may be used for schedulingof PDSCH in a cell. DCI format 1_0 may be a fallback DCI format (e.g.,with compact DCI payloads). DCI format 1_1 may be used for scheduling ofPDSCH in a cell (e.g., with more DCI payloads than DCI format 1_0). DCIformat 2_0 may be used for providing a slot format indication to a groupof UEs. DCI format 2_1 may be used for notifying a group of UEs of aphysical resource block and/or OFDM symbol where the UE may assume notransmission is intended to the UE. DCI format 2_2 may be used fortransmission of a transmit power control (TPC) command for PUCCH orPUSCH. DCI format 2_3 may be used for transmission of a group of TPCcommands for SRS transmissions by one or more UEs. DCI format(s) for newfunctions may be defined in future releases. DCI formats may havedifferent DCI sizes, or may share the same DCI size.

After scrambling a DCI with a RNTI, the base station may process the DCIwith channel coding (e.g., polar coding), rate matching, scramblingand/or QPSK modulation. A base station may map the coded and modulatedDCI on resource elements used and/or configured for a PDCCH. Based on apayload size of the DCI and/or a coverage of the base station, the basestation may transmit the DCI via a PDCCH occupying a number ofcontiguous control channel elements (CCEs). The number of the contiguousCCEs (referred to as aggregation level) may be 1, 2, 4, 8, 16, and/orany other suitable number. A CCE may comprise a number (e.g., 6) ofresource-element groups (REGs). A REG may comprise a resource block inan OFDM symbol. The mapping of the coded and modulated DCI on theresource elements may be based on mapping of CCEs and REGs (e.g.,CCE-to-REG mapping).

FIG. 14A illustrates an example of CORESET configurations for abandwidth part. The base station may transmit a DCI via a PDCCH on oneor more control resource sets (CORESETs). A CORESET may comprise atime-frequency resource in which the UE tries to decode a DCI using oneor more search spaces. The base station may configure a CORESET in thetime-frequency domain. In the example of FIG. 14A, a first CORESET 1401and a second CORESET 1402 occur at the first symbol in a slot. The firstCORESET 1401 overlaps with the second CORESET 1402 in the frequencydomain. A third CORESET 1403 occurs at a third symbol in the slot. Afourth CORESET 1404 occurs at the seventh symbol in the slot. CORESETsmay have a different number of resource blocks in frequency domain.

FIG. 14B illustrates an example of a CCE-to-REG mapping for DCItransmission on a CORESET and PDCCH processing. The CCE-to-REG mappingmay be an interleaved mapping (e.g., for the purpose of providingfrequency diversity) or a non-interleaved mapping (e.g., for thepurposes of facilitating interference coordination and/orfrequency-selective transmission of control channels). The base stationmay perform different or same CCE-to-REG mapping on different CORESETs.A CORESET may be associated with a CCE-to-REG mapping by RRCconfiguration. A CORESET may be configured with an antenna port quasico-location (QCL) parameter. The antenna port QCL parameter may indicateQCL information of a demodulation reference signal (DMRS) for PDCCHreception in the CORESET.

The base station may transmit, to the UE, RRC messages comprisingconfiguration parameters of one or more CORESETs and one or more searchspace sets. The configuration parameters may indicate an associationbetween a search space set and a CORESET. A search space set maycomprise a set of PDCCH candidates formed by CCEs at a given aggregationlevel. The configuration parameters may indicate: a number of PDCCHcandidates to be monitored per aggregation level; a PDCCH monitoringperiodicity and a PDCCH monitoring pattern; one or more DCI formats tobe monitored by the UE; and/or whether a search space set is a commonsearch space set or a UE-specific search space set. A set of CCEs in thecommon search space set may be predefined and known to the UE. A set ofCCEs in the UE-specific search space set may be configured based on theUE’s identity (e.g., C-RNTI).

As shown in FIG. 14B, the UE may determine a time-frequency resource fora CORESET based on RRC messages. The UE may determine a CCE-to-REGmapping (e.g., interleaved or non-interleaved, and/or mappingparameters) for the CORESET based on configuration parameters of theCORESET. The UE may determine a number (e.g., at most 10) of searchspace sets configured on the CORESET based on the RRC messages. The UEmay monitor a set of PDCCH candidates according to configurationparameters of a search space set. The UE may monitor a set of PDCCHcandidates in one or more CORESETs for detecting one or more DCIs.Monitoring may comprise decoding one or more PDCCH candidates of the setof the PDCCH candidates according to the monitored DCI formats.Monitoring may comprise decoding a DCI content of one or more PDCCHcandidates with possible (or configured) PDCCH locations, possible (orconfigured) PDCCH formats (e.g., number of CCEs, number of PDCCHcandidates in common search spaces, and/or number of PDCCH candidates inthe UE-specific search spaces) and possible (or configured) DCI formats.The decoding may be referred to as blind decoding. The UE may determinea DCI as valid for the UE, in response to CRC checking (e.g., scrambledbits for CRC parity bits of the DCI matching a RNTI value). The UE mayprocess information contained in the DCI (e.g., a scheduling assignment,an uplink grant, power control, a slot format indication, a downlinkpreemption, and/or the like).

The UE may transmit uplink control signaling (e.g., uplink controlinformation (UCI)) to a base station. The uplink control signaling maycomprise hybrid automatic repeat request (HARQ) acknowledgements forreceived DL-SCH transport blocks. The UE may transmit the HARQacknowledgements after receiving a DL-SCH transport block. Uplinkcontrol signaling may comprise channel state information (CSI)indicating channel quality of a physical downlink channel. The UE maytransmit the CSI to the base station. The base station, based on thereceived CSI, may determine transmission format parameters (e.g.,comprising multi-antenna and beamforming schemes) for a downlinktransmission. Uplink control signaling may comprise scheduling requests(SR). The UE may transmit an SR indicating that uplink data is availablefor transmission to the base station. The UE may transmit a UCI (e.g.,HARQ acknowledgements (HARQ-ACK), CSI report, SR, and the like) via aphysical uplink control channel (PUCCH) or a physical uplink sharedchannel (PUSCH). The UE may transmit the uplink control signaling via aPUCCH using one of several PUCCH formats.

There may be five PUCCH formats and the UE may determine a PUCCH formatbased on a size of the UCI (e.g., a number of uplink symbols of UCItransmission and a number of UCI bits). PUCCH format 0 may have a lengthof one or two OFDM symbols and may include two or fewer bits. The UE maytransmit UCI in a PUCCH resource using PUCCH format 0 if thetransmission is over one or two symbols and the number of HARQ-ACKinformation bits with positive or negative SR (HARQ-ACK/SR bits) is oneor two. PUCCH format 1 may occupy a number between four and fourteenOFDM symbols and may include two or fewer bits. The UE may use PUCCHformat 1 if the transmission is four or more symbols and the number ofHARQ-ACK/SR bits is one or two. PUCCH format 2 may occupy one or twoOFDM symbols and may include more than two bits. The UE may use PUCCHformat 2 if the transmission is over one or two symbols and the numberof UCI bits is two or more. PUCCH format 3 may occupy a number betweenfour and fourteen OFDM symbols and may include more than two bits. TheUE may use PUCCH format 3 if the transmission is four or more symbols,the number of UCI bits is two or more and PUCCH resource does notinclude an orthogonal cover code. PUCCH format 4 may occupy a numberbetween four and fourteen OFDM symbols and may include more than twobits. The UE may use PUCCH format 4 if the transmission is four or moresymbols, the number of UCI bits is two or more and the PUCCH resourceincludes an orthogonal cover code.

The base station may transmit configuration parameters to the UE for aplurality of PUCCH resource sets using, for example, an RRC message. Theplurality of PUCCH resource sets (e.g., up to four sets) may beconfigured on an uplink BWP of a cell. A PUCCH resource set may beconfigured with a PUCCH resource set index, a plurality of PUCCHresources with a PUCCH resource being identified by a PUCCH resourceidentifier (e.g., pucch-Resourceid), and/or a number (e.g. a maximumnumber) of UCI information bits the UE may transmit using one of theplurality of PUCCH resources in the PUCCH resource set. When configuredwith a plurality of PUCCH resource sets, the UE may select one of theplurality of PUCCH resource sets based on a total bit length of the UCIinformation bits (e.g., HARQ-ACK, SR, and/or CSI). If the total bitlength of UCI information bits is two or fewer, the UE may select afirst PUCCH resource set having a PUCCH resource set index equal to “0”.If the total bit length of UCI information bits is greater than two andless than or equal to a first configured value, the UE may select asecond PUCCH resource set having a PUCCH resource set index equal to“1”. If the total bit length of UCI information bits is greater than thefirst configured value and less than or equal to a second configuredvalue, the UE may select a third PUCCH resource set having a PUCCHresource set index equal to “2”. If the total bit length of UCIinformation bits is greater than the second configured value and lessthan or equal to a third value (e.g., 1406), the UE may select a fourthPUCCH resource set having a PUCCH resource set index equal to “3”.

After determining a PUCCH resource set from a plurality of PUCCHresource sets, the UE may determine a PUCCH resource from the PUCCHresource set for UCI (HARQ-ACK, CSI, and/or SR) transmission. The UE maydetermine the PUCCH resource based on a PUCCH resource indicator in aDCI (e.g., with a DCI format 1_0 or DCI for 1_1) received on a PDCCH. Athree-bit PUCCH resource indicator in the DCI may indicate one of eightPUCCH resources in the PUCCH resource set. Based on the PUCCH resourceindicator, the UE may transmit the UCI (HARQ-ACK, CSI and/or SR) using aPUCCH resource indicated by the PUCCH resource indicator in the DCI.

FIG. 15 illustrates an example of a wireless device 1502 incommunication with a base station 1504 in accordance with embodiments ofthe present disclosure. The wireless device 1502 and base station 1504may be part of a mobile communication network, such as the mobilecommunication network 100 illustrated in FIG. 1A, the mobilecommunication network 150 illustrated in FIG. 1B, or any othercommunication network. Only one wireless device 1502 and one basestation 1504 are illustrated in FIG. 15 , but it will be understood thata mobile communication network may include more than one UE and/or morethan one base station, with the same or similar configuration as thoseshown in FIG. 15 .

The base station 1504 may connect the wireless device 1502 to a corenetwork (not shown) through radio communications over the air interface(or radio interface) 1506. The communication direction from the basestation 1504 to the wireless device 1502 over the air interface 1506 isknown as the downlink, and the communication direction from the wirelessdevice 1502 to the base station 1504 over the air interface is known asthe uplink. Downlink transmissions may be separated from uplinktransmissions using FDD, TDD, and/or some combination of the twoduplexing techniques.

In the downlink, data to be sent to the wireless device 1502 from thebase station 1504 may be provided to the processing system 1508 of thebase station 1504. The data may be provided to the processing system1508 by, for example, a core network. In the uplink, data to be sent tothe base station 1504 from the wireless device 1502 may be provided tothe processing system 1518 of the wireless device 1502. The processingsystem 1508 and the processing system 1518 may implement layer 3 andlayer 2 OSI functionality to process the data for transmission. Layer 2may include an SDAP layer, a PDCP layer, an RLC layer, and a MAC layer,for example, with respect to FIG. 2A, FIG. 2B, FIG. 3 , and FIG. 4A.Layer 3 may include an RRC layer as with respect to FIG. 2B.

After being processed by processing system 1508, the data to be sent tothe wireless device 1502 may be provided to a transmission processingsystem 1510 of base station 1504. Similarly, after being processed bythe processing system 1518, the data to be sent to base station 1504 maybe provided to a transmission processing system 1520 of the wirelessdevice 1502. The transmission processing system 1510 and thetransmission processing system 1520 may implement layer 1 OSIfunctionality. Layer 1 may include a PHY layer with respect to FIG. 2A,FIG. 2B, FIG. 3 , and FIG. 4A. For transmit processing, the PHY layermay perform, for example, forward error correction coding of transportchannels, interleaving, rate matching, mapping of transport channels tophysical channels, modulation of physical channel, multiple-inputmultiple-output (MIMO) or multi-antenna processing, and/or the like.

At the base station 1504, a reception processing system 1512 may receivethe uplink transmission from the wireless device 1502. At the wirelessdevice 1502, a reception processing system 1522 may receive the downlinktransmission from base station 1504. The reception processing system1512 and the reception processing system 1522 may implement layer 1 OSIfunctionality. Layer 1 may include a PHY layer with respect to FIG. 2A,FIG. 2B, FIG. 3 , and FIG. 4A. For receive processing, the PHY layer mayperform, for example, error detection, forward error correctiondecoding, deinterleaving, demapping of transport channels to physicalchannels, demodulation of physical channels, MIMO or multi-antennaprocessing, and/or the like.

As shown in FIG. 15 , a wireless device 1502 and the base station 1504may include multiple antennas. The multiple antennas may be used toperform one or more MIMO or multi-antenna techniques, such as spatialmultiplexing (e.g., single-user MIMO or multi-user MIMO),transmit/receive diversity, and/or beamforming. In other examples, thewireless device 1502 and/or the base station 1504 may have a singleantenna.

The processing system 1508 and the processing system 1518 may beassociated with a memory 1514 and a memory 1524, respectively. Memory1514 and memory 1524 (e.g., one or more non-transitory computer readablemediums) may store computer program instructions or code that may beexecuted by the processing system 1508 and/or the processing system 1518to carry out one or more of the functionalities discussed in the presentapplication. Although not shown in FIG. 15 , the transmission processingsystem 1510, the transmission processing system 1520, the receptionprocessing system 1512, and/or the reception processing system 1522 maybe coupled to a memory (e.g., one or more non-transitory computerreadable mediums) storing computer program instructions or code that maybe executed to carry out one or more of their respectivefunctionalities.

The processing system 1508 and/or the processing system 1518 maycomprise one or more controllers and/or one or more processors. The oneor more controllers and/or one or more processors may comprise, forexample, a general-purpose processor, a digital signal processor (DSP),a microcontroller, an application specific integrated circuit (ASIC), afield programmable gate array (FPGA) and/or other programmable logicdevice, discrete gate and/or transistor logic, discrete hardwarecomponents, an on-board unit, or any combination thereof. The processingsystem 1508 and/or the processing system 1518 may perform at least oneof signal coding/processing, data processing, power control,input/output processing, and/or any other functionality that may enablethe wireless device 1502 and the base station 1504 to operate in awireless environment.

The processing system 1508 and/or the processing system 1518 may beconnected to one or more peripherals 1516 and one or more peripherals1526, respectively. The one or more peripherals 1516 and the one or moreperipherals 1526 may include software and/or hardware that providefeatures and/or functionalities, for example, a speaker, a microphone, akeypad, a display, a touchpad, a power source, a satellite transceiver,a universal serial bus (USB) port, a hands-free headset, a frequencymodulated (FM) radio unit, a media player, an Internet browser, anelectronic control unit (e.g., for a motor vehicle), and/or one or moresensors (e.g., an accelerometer, a gyroscope, a temperature sensor, aradar sensor, a lidar sensor, an ultrasonic sensor, a light sensor, acamera, and/or the like). The processing system 1508 and/or theprocessing system 1518 may receive user input data from and/or provideuser output data to the one or more peripherals 1516 and/or the one ormore peripherals 1526. The processing system 1518 in the wireless device1502 may receive power from a power source and/or may be configured todistribute the power to the other components in the wireless device1502. The power source may comprise one or more sources of power, forexample, a battery, a solar cell, a fuel cell, or any combinationthereof. The processing system 1508 and/or the processing system 1518may be connected to a GPS chipset 1517 and a GPS chipset 1527,respectively. The GPS chipset 1517 and the GPS chipset 1527 may beconfigured to provide geographic location information of the wirelessdevice 1502 and the base station 1504, respectively.

FIG. 16A illustrates an example structure for uplink transmission. Abaseband signal representing a physical uplink shared channel mayperform one or more functions. The one or more functions may comprise atleast one of: scrambling; modulation of scrambled bits to generatecomplex-valued symbols; mapping of the complex-valued modulation symbolsonto one or several transmission layers; transform precoding to generatecomplex-valued symbols; precoding of the complex-valued symbols; mappingof precoded complex-valued symbols to resource elements; generation ofcomplex-valued time-domain Single Carrier-Frequency Division MultipleAccess (SC-FDMA) or CP-OFDM signal for an antenna port; and/or the like.In an example, when transform precoding is enabled, a SC-FDMA signal foruplink transmission may be generated. In an example, when transformprecoding is not enabled, an CP-OFDM signal for uplink transmission maybe generated by FIG. 16A. These functions are illustrated as examplesand it is anticipated that other mechanisms may be implemented invarious embodiments.

FIG. 16B illustrates an example structure for modulation andup-conversion of a baseband signal to a carrier frequency. The basebandsignal may be a complex-valued SC-FDMA or CP-OFDM baseband signal for anantenna port and/or a complex-valued Physical Random Access Channel(PRACH) baseband signal. Filtering may be employed prior totransmission.

FIG. 16C illustrates an example structure for downlink transmissions. Abaseband signal representing a physical downlink channel may perform oneor more functions. The one or more functions may comprise: scrambling ofcoded bits in a codeword to be transmitted on a physical channel;modulation of scrambled bits to generate complex-valued modulationsymbols; mapping of the complex-valued modulation symbols onto one orseveral transmission layers; precoding of the complex-valued modulationsymbols on a layer for transmission on the antenna ports; mapping ofcomplex-valued modulation symbols for an antenna port to resourceelements; generation of complex-valued time-domain OFDM signal for anantenna port; and/or the like. These functions are illustrated asexamples and it is anticipated that other mechanisms may be implementedin various embodiments.

FIG. 16D illustrates another example structure for modulation andup-conversion of a baseband signal to a carrier frequency. The basebandsignal may be a complex-valued OFDM baseband signal for an antenna port.Filtering may be employed prior to transmission.

A wireless device may receive from a base station one or more messages(e.g. RRC messages) comprising configuration parameters of a pluralityof cells (e.g. primary cell, secondary cell). The wireless device maycommunicate with at least one base station (e.g. two or more basestations in dual-connectivity) via the plurality of cells. The one ormore messages (e.g. as a part of the configuration parameters) maycomprise parameters of physical, MAC, RLC, PCDP, SDAP, RRC layers forconfiguring the wireless device. For example, the configurationparameters may comprise parameters for configuring physical and MAClayer channels, bearers, etc. For example, the configuration parametersmay comprise parameters indicating values of timers for physical, MAC,RLC, PCDP, SDAP, RRC layers, and/or communication channels.

A timer may begin running once it is started and continue running untilit is stopped or until it expires. A timer may be started if it is notrunning or restarted if it is running. A timer may be associated with avalue (e.g. the timer may be started or restarted from a value or may bestarted from zero and expire once it reaches the value). The duration ofa timer may not be updated until the timer is stopped or expires (e.g.,due to BWP switching). A timer may be used to measure a timeperiod/window for a process. When the specification refers to animplementation and procedure related to one or more timers, it will beunderstood that there are multiple ways to implement the one or moretimers. For example, it will be understood that one or more of themultiple ways to implement a timer may be used to measure a timeperiod/window for the procedure. For example, a random access responsewindow timer may be used for measuring a window of time for receiving arandom access response. In an example, instead of starting and expiry ofa random access response window timer, the time difference between twotime stamps may be used. When a timer is restarted, a process formeasurement of time window may be restarted. Other exampleimplementations may be provided to restart a measurement of a timewindow.

A gNB may transmit one or more MAC PDUs to a wireless device. In anexample, a MAC PDU may be a bit string that is byte aligned (e.g., amultiple of eight bits) in length. In an example, bit strings may berepresented by tables in which the most significant bit is the leftmostbit of the first line of the table, and the least significant bit is therightmost bit on the last line of the table. More generally, the bitstring may be read from left to right and then in the reading order ofthe lines. In an example, the bit order of a parameter field within aMAC PDU is represented with the first and most significant bit in theleftmost bit and the last and least significant bit in the rightmostbit.

In an example, a MAC SDU may be a bit string that is byte aligned (e.g.,a multiple of eight bits) in length. In an example, a MAC SDU may beincluded in a MAC PDU from the first bit onward. A MAC CE may be a bitstring that is byte aligned (e.g., a multiple of eight bits) in length.A MAC subheader may be a bit string that is byte aligned (e.g., amultiple of eight bits) in length. In an example, a MAC subheader may beplaced immediately in front of a corresponding MAC SDU, MAC CE, orpadding. A MAC entity may ignore a value of reserved bits in a DL MACPDU.

In an example, a MAC PDU may comprise one or more MAC subPDUs. A MACsubPDU of the one or more MAC subPDUs may comprise: a MAC subheader only(including padding); a MAC subheader and a MAC SDU; a MAC subheader anda MAC CE; and/or a MAC subheader and padding. The MAC SDU may be ofvariable size. A MAC subheader may correspond to a MAC SDU, a MAC CE, orpadding.

In an example, when a MAC subheader corresponds to a MAC SDU, avariable-sized MAC CE, or padding, the MAC subheader may comprise: an Rfield with a one bit length; an F field with a one bit length; an LCIDfield with a multi-bit length; and/or an L field with a multi-bitlength.

FIG. 17A shows an example of a MAC subheader with an R field, an Ffield, an LCID field, and an L field. In the example MAC subheader ofFIG. 17A, the LCID field may be six bits in length, and the L field maybe eight bits in length. FIG. 17B shows example of a MAC subheader withan R field, a F field, an LCID field, and an L field. In the example MACsubheader of FIG. 17B, the LCID field may be six bits in length, and theL field may be sixteen bits in length. When a MAC subheader correspondsto a fixed sized MAC CE or padding, the MAC subheader may comprise: an Rfield with a two bit length and an LCID field with a multi-bit length.FIG. 17C shows an example of a MAC subheader with an R field and an LCIDfield. In the example MAC subheader of FIG. 17C, the LCID field may besix bits in length, and the R field may be two bits in length.

FIG. 18A shows an example of a DL MAC PDU. Multiple MAC CEs, such as MACCE 1 and 2, may be placed together. A MAC subPDU comprising a MAC CE maybe placed before any MAC subPDU comprising a MAC SDU or a MAC subPDUcomprising padding. FIG. 18B shows an example of a UL MAC PDU. MultipleMAC CEs, such as MAC CE 1 and 2, may be placed together. A MAC subPDUcomprising a MAC CE may be placed after all MAC subPDUs comprising a MACSDU. In addition, the MAC subPDU may be placed before a MAC subPDUcomprising padding.

In an example, a MAC entity of a gNB may transmit one or more MAC CEs toa MAC entity of a wireless device. FIG. 19 shows an example of multipleLCIDs that may be associated with the one or more MAC CEs. The one ormore MAC CEs comprise at least one of: a SP ZP CSI-RS Resource SetActivation/Deactivation MAC CE, a PUCCH spatial relationActivation/Deactivation MAC CE, a SP SRS Activation/Deactivation MAC CE,a SP CSI reporting on PUCCH Activation/Deactivation MAC CE, a TCI StateIndication for UE-specific PDCCH MAC CE, a TCI State Indication forUE-specific PDSCH MAC CE, an Aperiodic CSI Trigger State SubselectionMAC CE, a SP CSI-RS/CSI-IM Resource Set Activation/Deactivation MAC CE,a UE contention resolution identity MAC CE, a timing advance command MACCE, a DRX command MAC CE, a Long DRX command MAC CE, an SCellactivation/deactivation MAC CE (1 Octet), an SCellactivation/deactivation MAC CE (4 Octet), and/or a duplicationactivation/deactivation MAC CE. In an example, a MAC CE, such as a MACCE transmitted by a MAC entity of a gNB to a MAC entity of a wirelessdevice, may have an LCID in the MAC subheader corresponding to the MACCE. Different MAC CE may have different LCID in the MAC subheadercorresponding to the MAC CE. For example, an LCID given by 111011 in aMAC subheader may indicate that a MAC CE associated with the MACsubheader is a long DRX command MAC CE.

In an example, the MAC entity of the wireless device may transmit to theMAC entity of the gNB one or more MAC CEs. FIG. 20 shows an example ofthe one or more MAC CEs. The one or more MAC CEs may comprise at leastone of: a short buffer status report (BSR) MAC CE, a long BSR MAC CE, aC-RNTI MAC CE, a configured grant confirmation MAC CE, a single entryPHR MAC CE, a multiple entry PHR MAC CE, a short truncated BSR, and/or along truncated BSR. In an example, a MAC CE may have an LCID in the MACsubheader corresponding to the MAC CE. Different MAC CE may havedifferent LCID in the MAC subheader corresponding to the MAC CE. Forexample, an LCID given by 111011 in a MAC subheader may indicate that aMAC CE associated with the MAC subheader is a short-truncated commandMAC CE.

In carrier aggregation (CA), two or more component carriers (CCs) may beaggregated. A wireless device may simultaneously receive or transmit onone or more CCs, depending on capabilities of the wireless device, usingthe technique of CA. In an example, a wireless device may support CA forcontiguous CCs and/or for non-contiguous CCs. CCs may be organized intocells. For example, CCs may be organized into one primary cell (PCell)and one or more secondary cells (SCells). When configured with CA, awireless device may have one RRC connection with a network. During anRRC connection establishment/re-establishment/handover, a cell providingNAS mobility information may be a serving cell. During an RRC connectionre-establishment/handover procedure, a cell providing a security inputmay be a serving cell. In an example, the serving cell may denote aPCell. In an example, a gNB may transmit, to a wireless device, one ormore messages comprising configuration parameters of a plurality of oneor more SCells, depending on capabilities of the wireless device.

When configured with CA, a base station and/or a wireless device mayemploy an activation/deactivation mechanism of an SCell to improvebattery or power consumption of the wireless device. When a wirelessdevice is configured with one or more SCells, a gNB may activate ordeactivate at least one of the one or more SCells. Upon configuration ofan SCell, the SCell may be deactivated unless an SCell state associatedwith the SCell is set to “activated” or “dormant”.

A wireless device may activate/deactivate an SCell in response toreceiving an SCell Activation/Deactivation MAC CE. In an example, a gNBmay transmit, to a wireless device, one or more messages comprising anSCell timer (e.g., sCellDeactivationTimer). In an example, a wirelessdevice may deactivate an SCell in response to an expiry of the SCelltimer.

When a wireless device receives an SCell Activation/Deactivation MAC CEactivating an SCell, the wireless device may activate the SCell. Inresponse to the activating the SCell, the wireless device may performoperations comprising SRS transmissions on the SCell; CQI/PMI/RI/CRIreporting for the SCell; PDCCH monitoring on the SCell; PDCCH monitoringfor the SCell; and/or PUCCH transmissions on the SCell. In response tothe activating the SCell, the wireless device may start or restart afirst SCell timer (e.g., sCellDeactivationTimer) associated with theSCell. The wireless device may start or restart the first SCell timer inthe slot when the SCell Activation/Deactivation MAC CE activating theSCell has been received. In an example, in response to the activatingthe SCell, the wireless device may (re-)initialize one or more suspendedconfigured uplink grants of a configured grant Type 1 associated withthe SCell according to a stored configuration. In an example, inresponse to the activating the SCell, the wireless device may triggerPHR.

When a wireless device receives an SCell Activation/Deactivation MAC CEdeactivating an activated SCell, the wireless device may deactivate theactivated SCell. In an example, when a first SCell timer (e.g.,sCellDeactivationTimer) associated with an activated SCell expires, thewireless device may deactivate the activated SCell. In response to thedeactivating the activated SCell, the wireless device may stop the firstSCell timer associated with the activated SCell. In an example, inresponse to the deactivating the activated SCell, the wireless devicemay clear one or more configured downlink assignments and/or one or moreconfigured uplink grants of a configured uplink grant Type 2 associatedwith the activated SCell. In an example, in response to the deactivatingthe activated SCell, the wireless device may: suspend one or moreconfigured uplink grants of a configured uplink grant Type 1 associatedwith the activated SCell; and/or flush HARQ buffers associated with theactivated SCell.

When an SCell is deactivated, a wireless device may not performoperations comprising: transmitting SRS on the SCell; reportingCQI/PMI/RI/CRI for the SCell; transmitting on UL-SCH on the SCell;transmitting on RACH on the SCell; monitoring at least one first PDCCHon the SCell; monitoring at least one second PDCCH for the SCell; and/ortransmitting a PUCCH on the SCell. When at least one first PDCCH on anactivated SCell indicates an uplink grant or a downlink assignment, awireless device may restart a first SCell timer (e.g.,sCellDeactivationTimer) associated with the activated SCell. In anexample, when at least one second PDCCH on a serving cell (e.g. a PCellor an SCell configured with PUCCH, i.e. PUCCH SCell) scheduling theactivated SCell indicates an uplink grant or a downlink assignment forthe activated SCell, a wireless device may restart the first SCell timer(e.g., sCellDeactivationTimer) associated with the activated SCell. Inan example, when an SCell is deactivated, if there is an ongoing randomaccess procedure on the SCell, a wireless device may abort the ongoingrandom access procedure on the SCell.

FIG. 21A shows an example of an SCell Activation/Deactivation MAC CE ofone octet. A first MAC PDU subheader with a first LCID (e.g., ‘111010’as shown in FIG. 19 ) may identify the SCell Activation/Deactivation MACCE of one octet. The SCell Activation/Deactivation MAC CE of one octetmay have a fixed size. The SCell Activation/Deactivation MAC CE of oneoctet may comprise a single octet. The single octet may comprise a firstnumber of C-fields (e.g. seven) and a second number of R-fields (e.g.,one). FIG. 21B shows an example of an SCell Activation/Deactivation MACCE of four octets. A second MAC PDU subheader with a second LCID (e.g.,‘111001’ as shown in FIG. 19 ) may identify the SCellActivation/Deactivation MAC CE of four octets. The SCellActivation/Deactivation MAC CE of four octets may have a fixed size. TheSCell Activation/Deactivation MAC CE of four octets may comprise fouroctets. The four octets may comprise a third number of C-fields (e.g.,31) and a fourth number of R-fields (e.g., 1).

In FIG. 21A and/or FIG. 21B, a C_(i) field may indicate anactivation/deactivation status of an SCell with an SCell index i if anSCell with SCell index i is configured. In an example, when the C_(i)field is set to one, an SCell with an SCell index i may be activated. Inan example, when the C_(i) field is set to zero, an SCell with an SCellindex i may be deactivated. In an example, if there is no SCellconfigured with SCell index i, the wireless device may ignore the C_(i)field. In FIG. 21A and FIG. 21B, an R field may indicate a reserved bit.The R field may be set to zero.

When configured with CA, a base station and/or a wireless device mayemploy a hibernation mechanism for an SCell to improve battery or powerconsumption of the wireless device and/or to improve latency of SCellactivation/addition. When the wireless device hibernates the SCell, theSCell may be transitioned into a dormant state. In response to the SCellbeing transitioned into a dormant state, the wireless device may: stoptransmitting SRS on the SCell; report CQI/PMI/RI/PTI/CRI for the SCellaccording to a periodicity configured for the SCell in a dormant state;not transmit on UL-SCH on the SCell; not transmit on RACH on the SCell;not monitor the PDCCH on the SCell; not monitor the PDCCH for the SCell;and/or not transmit PUCCH on the SCell. In an example, reporting CSI foran SCell and not monitoring the PDCCH on/for the SCell, when the SCellis in a dormant state, may provide the base station an always-updatedCSI for the SCell. With the always-updated CSI, the base station mayemploy a quick and/or accurate channel adaptive scheduling on the SCellonce the SCell is transitioned back into active state, thereby speedingup the activation procedure of the SCell. In an example, reporting CSIfor the SCell and not monitoring the PDCCH on/for the SCell, when theSCell is in dormant state, may improve battery or power consumption ofthe wireless device, while still providing the base station timelyand/or accurate channel information feedback. In an example, aPCell/PSCell and/or a PUCCH secondary cell may not be configured ortransitioned into dormant state.

When configured with one or more SCells, a gNB may activate, hibernate,or deactivate at least one of the one or more SCells. In an example, agNB may transmit one or more RRC messages comprising parametersindicating at least one SCell being set to an active state, a dormantstate, or an inactive state, to a wireless device. In an example, whenan SCell is in an active state, the wireless device may perform: SRStransmissions on the SCell; CQI/PMI/RI/CRI reporting for the SCell;PDCCH monitoring on the SCell; PDCCH monitoring for the SCell; and/orPUCCH/SPUCCH transmissions on the SCell.

When an SCell is in an inactive state, the wireless device may: nottransmit SRS on the SCell; not report CQI/PMI/RI/CRI for the SCell; nottransmit on UL-SCH on the SCell; not transmit on RACH on the SCell; notmonitor PDCCH on the SCell; not monitor PDCCH for the SCell; and/or nottransmit PUCCH/SPUCCH on the SCell. When an SCell is in a dormant state,the wireless device may: not transmit SRS on the SCell; reportCQI/PMI/RI/CRI for the SCell; not transmit on UL-SCH on the SCell; nottransmit on RACH on the SCell; not monitor PDCCH on the SCell; notmonitor PDCCH for the SCell; and/or not transmit PUCCH/SPUCCH on theSCell. When configured with one or more SCells, a gNB may activate,hibernate, or deactivate at least one of the one or more SCells. In anexample, a gNB may transmit one or more MAC control elements comprisingparameters indicating activation, deactivation, or hibernation of atleast one SCell to a wireless device.

In an example, a gNB may transmit a first MAC CE (e.g.,activation/deactivation MAC CE, as shown in FIG. 21A or FIG. 21B)indicating activation or deactivation of at least one SCell to awireless device. In FIG. 21A and/or FIG. 21B, a C_(i) field may indicatean activation/deactivation status of an SCell with an SCell index i ifan SCell with SCell index i is configured. In an example, when the C_(i)field is set to one, an SCell with an SCell index i may be activated. Inan example, when the C_(i) field is set to zero, an SCell with an SCellindex i may be deactivated. In an example, if there is no SCellconfigured with SCell index i, the wireless device may ignore the C_(i)field. In FIG. 21A and FIG. 21B, an R field may indicate a reserved bit.In an example, the R field may be set to zero.

In an example, a gNB may transmit a second MAC CE (e.g., hibernation MACCE) indicating activation or hibernation of at least one SCell to awireless device. In an example, the second MAC CE may be associated witha second LCID different from a first LCID of the first MAC CE (e.g.,activation/deactivation MAC CE). In an example, the second MAC CE mayhave a fixed size. In an example, the second MAC CE may consist of asingle octet containing seven C-fields and one R-field. FIG. 22A showsan example of the second MAC CE with a single octet. In another example,the second MAC CE may consist of four octets containing 31 C-fields andone R-field. FIG. 22B shows an example of the second MAC CE with fouroctets. In an example, the second MAC CE with four octets may beassociated with a third LCID different from the second LCID for thesecond MAC CE with a single octet, and/or the first LCID foractivation/deactivation MAC CE. In an example, when there is no SCellwith a serving cell index greater than 7, the second MAC CE of one octetmay be applied, otherwise the second MAC CE of four octets may beapplied.

In an example, when the second MAC CE is received, and the first MAC CEis not received, C_(i) may indicate a dormant/activated status of anSCell with SCell index i if there is an SCell configured with SCellindex i, otherwise the MAC entity may ignore the C_(i) field. In anexample, when C_(i) is set to “1”, the wireless device may transition anSCell associated with SCell index i into a dormant state. In an example,when C_(i) is set to “0”, the wireless device may activate an SCellassociated with SCell index i. In an example, when C_(i) is set to “0”and the SCell with SCell index i is in a dormant state, the wirelessdevice may activate the SCell with SCell index i. In an example, whenC_(i) is set to “0” and the SCell with SCell index i is not in a dormantstate, the wireless device may ignore the C_(i) field.

In an example, when both the first MAC CE (activation/deactivation MACCE) and the second MAC CE (hibernation MAC CE) are received, two C_(i)fields of the two MAC CEs may indicate possible state transitions of theSCell with SCell index i if there is an SCell configured with SCellindex i, otherwise the MAC entity may ignore the C_(i) fields. In anexample, the C_(i) fields of the two MAC CEs may be interpretedaccording to FIG. 22C.

When configured with one or more SCells, a gNB may activate, hibernate,or deactivate at least one of the one or more SCells. In an example, aMAC entity of a gNB and/or a wireless device may maintain an SCelldeactivation timer (e.g., sCellDeactivationTimer) per configured SCell(except the SCell configured with PUCCH/SPUCCH, if any) and deactivatethe associated SCell upon its expiry.

In an example, a MAC entity of a gNB and/or a wireless device maymaintain an SCell hibernation timer (e.g., sCellHibernationTimer) perconfigured SCell (except the SCell configured with PUCCH/SPUCCH, if any)and hibernate the associated SCell upon the SCell hibernation timerexpiry if the SCell is in active state. In an example, when both theSCell deactivation timer and the SCell hibernation timer are configured,the SCell hibernation timer may take priority over the SCelldeactivation timer. In an example, when both the SCell deactivationtimer and the SCell hibernation timer are configured, a gNB and/or awireless device may ignore the SCell deactivation timer regardless ofthe SCell deactivation timer expiry.

In an example, a MAC entity of a gNB and/or a wireless device maymaintain a dormant SCell deactivation timer (e.g.,dormantSCellDeactivationTimer) per configured SCell (except the SCellconfigured with PUCCH/SPUCCH, if any), and deactivate the associatedSCell upon the dormant SCell deactivation timer expiry if the SCell isin dormant state.

In an example, when a MAC entity of a wireless device is configured withan activated SCell upon SCell configuration, the MAC entity may activatethe SCell. In an example, when a MAC entity of a wireless devicereceives a MAC CE(s) activating an SCell, the MAC entity may activatethe SCell. In an example, the MAC entity may start or restart the SCelldeactivation timer associated with the SCell in response to activatingthe SCell. In an example, the MAC entity may start or restart the SCellhibernation timer (if configured) associated with the SCell in responseto activating the SCell. In an example, the MAC entity may trigger PHRprocedure in response to activating the SCell.

In an example, when a MAC entity of a wireless device receives a MACCE(s) indicating deactivating an SCell, the MAC entity may deactivatethe SCell. In an example, in response to receiving the MAC CE(s), theMAC entity may: deactivate the SCell; stop an SCell deactivation timerassociated with the SCell; and/or flush all HARQ buffers associated withthe SCell. In an example, when an SCell deactivation timer associatedwith an activated SCell expires and an SCell hibernation timer is notconfigured, the MAC entity may: deactivate the SCell; stop the SCelldeactivation timer associated with the SCell; and/or flush all HARQbuffers associated with the SCell.

In an example, when a first PDCCH on an activated SCell indicates anuplink grant or downlink assignment, or a second PDCCH on a serving cellscheduling an activated SCell indicates an uplink grant or a downlinkassignment for the activated SCell, or a MAC PDU is transmitted in aconfigured uplink grant or received in a configured downlink assignment,the MAC entity may: restart the SCell deactivation timer associated withthe SCell; and/or restart the SCell hibernation timer associated withthe SCell if configured. In an example, when an SCell is deactivated, anongoing random access procedure on the SCell may be aborted.

In an example, when a MAC entity is configured with an SCell associatedwith an SCell state set to dormant state upon the SCell configuration,or when the MAC entity receives MAC CE(s) indicating transitioning theSCell into a dormant state, the MAC entity may: transition the SCellinto a dormant state; transmit one or more CSI reports for the SCell;stop an SCell deactivation timer associated with the SCell; stop anSCell hibernation timer associated with the SCell if configured; startor restart a dormant SCell deactivation timer associated with the SCell;and/or flush all HARQ buffers associated with the SCell. In an example,when the SCell hibernation timer associated with the activated SCellexpires, the MAC entity may: hibernate the SCell; stop the SCelldeactivation timer associated with the SCell; stop the SCell hibernationtimer associated with the SCell; and/or flush all HARQ buffersassociated with the SCell. In an example, when a dormant SCelldeactivation timer associated with a dormant SCell expires, the MACentity may: deactivate the SCell; and/or stop the dormant SCelldeactivation timer associated with the SCell. In an example, when anSCell is in dormant state, ongoing random access procedure on the SCellmay be aborted.

A base station (gNB) may configure a wireless device (UE) with uplink(UL) bandwidth parts (BWPs) and downlink (DL) BWPs to enable bandwidthadaptation (BA) on a PCell. If carrier aggregation is configured, thegNB may further configure the UE with at least DL BWP(s) (i.e., theremay be no UL BWPs in the UL) to enable BA on an SCell. For the PCell, aninitial active BWP may be a first BWP used for initial access. For theSCell, a first active BWP may be a second BWP configured for the UE tooperate on the SCell upon the SCell being activated. In paired spectrum(e.g. FDD), a gNB and/or a UE may independently switch a DL BWP and anUL BWP. In unpaired spectrum (e.g. TDD), a gNB and/or a UE maysimultaneously switch a DL BWP and an UL BWP.

In an example, a gNB and/or a UE may switch a BWP between configuredBWPs by means of a DCI or a BWP inactivity timer. When the BWPinactivity timer is configured for a serving cell, the gNB and/or the UEmay switch an active BWP to a default BWP in response to an expiry ofthe BWP inactivity timer associated with the serving cell. The defaultBWP may be configured by the network. In an example, for FDD systems,when configured with BA, one UL BWP for each uplink carrier and one DLBWP may be active at a time in an active serving cell. In an example,for TDD systems, one DL/UL BWP pair may be active at a time in an activeserving cell. Operating on the one UL BWP and the one DL BWP (or the oneDL/UL pair) may improve UE battery consumption. BWPs other than the oneactive UL BWP and the one active DL BWP that the UE may work on may bedeactivated. On deactivated BWPs, the UE may: not monitor PDCCH; and/ornot transmit on PUCCH, PRACH, and UL-SCH.

In an example, a serving cell may be configured with at most a firstnumber (e.g., four) of BWPs. In an example, for an activated servingcell, there may be one active BWP at any point in time. In an example, aBWP switching for a serving cell may be used to activate an inactive BWPand deactivate an active BWP at a time. In an example, the BWP switchingmay be controlled by a PDCCH indicating a downlink assignment or anuplink grant. In an example, the BWP switching may be controlled by aBWP inactivity timer (e.g., bwp-InactivityTimer). In an example, the BWPswitching may be controlled by a MAC entity in response to initiating aRandom Access procedure. Upon addition of an SpCell or activation of anSCell, one BWP may be initially active without receiving a PDCCHindicating a downlink assignment or an uplink grant. The active BWP fora serving cell may be indicated by RRC and/or PDCCH. In an example, forunpaired spectrum, a DL BWP may be paired with a UL BWP, and BWPswitching may be common for both UL and DL.

FIG. 23 shows an example of BWP switching on an SCell. In an example, aUE may receive RRC message comprising parameters of a SCell and one ormore BWP configuration associated with the SCell. The RRC message maycomprise: RRC connection reconfiguration message (e.g.,RRCReconfiguration); RRC connection reestablishment message (e.g.,RRCRestablishment); and/or RRC connection setup message (e.g.,RRCSetup). Among the one or more BWPs, at least one BWP may beconfigured as the first active BWP (e.g., BWP 1 in FIG. 23 ), one BWP asthe default BWP (e.g., BWP 0 in FIG. 23 ). The UE may receive a MAC CEto activate the SCell at n^(th) slot. The UE may start a SCelldeactivation timer (e.g., sCellDeactivationTimer), and start CSI relatedactions for the SCell, and/or start CSI related actions for the firstactive BWP of the SCell. The UE may start monitoring a PDCCH on BWP 1 inresponse to activating the SCell.

In an example, the UE may start restart a BWP inactivity timer (e.g.,bwp-InactivityTimer) at m-th slot in response to receiving a DCIindicating DL assignment on BWP 1. The UE may switch back to the defaultBWP (e.g., BWP 0) as an active BWP when the BWP inactivity timerexpires, at s-th slot. The UE may deactivate the SCell and/or stop theBWP inactivity timer when the sCellDeactivationTimer expires.

In an example, a MAC entity may apply normal operations on an active BWPfor an activated serving cell configured with a BWP comprising:transmitting on UL-SCH; transmitting on RACH; monitoring a PDCCH;transmitting PUCCH; receiving DL-SCH; and/or (re-) initializing anysuspended configured uplink grants of configured grant Type 1 accordingto a stored configuration, if any.

In an example, on an inactive BWP for each activated serving cellconfigured with a BWP, a MAC entity may: not transmit on UL-SCH; nottransmit on RACH; not monitor a PDCCH; not transmit PUCCH; not transmitSRS, not receive DL-SCH; clear any configured downlink assignment andconfigured uplink grant of configured grant Type 2; and/or suspend anyconfigured uplink grant of configured Type 1.

In an example, if a MAC entity receives a PDCCH for a BWP switching of aserving cell while a Random Access procedure associated with thisserving cell is not ongoing, a UE may perform the BWP switching to a BWPindicated by the PDCCH. In an example, if a bandwidth part indicatorfield is configured in DCI format 1_1, the bandwidth part indicatorfield value may indicate the active DL BWP, from the configured DL BWPset, for DL receptions. In an example, if a bandwidth part indicatorfield is configured in DCI format 0_1, the bandwidth part indicatorfield value may indicate the active UL BWP, from the configured UL BWPset, for UL transmissions.

In an example, for a primary cell, a UE may be provided by a higherlayer parameter Default-DL-BWP a default DL BWP among the configured DLBWPs. If a UE is not provided a default DL BWP by the higher layerparameter Default-DL-BWP, the default DL BWP is the initial active DLBWP. In an example, a UE may be provided by higher layer parameterbwp-InactivityTimer, a timer value for the primary cell. If configured,the UE may increment the timer, if running, every interval of 1millisecond for frequency range 1 or every 0.5 milliseconds forfrequency range 2 if the UE may not detect a DCI format 1_1 for pairedspectrum operation or if the UE may not detect a DCI format 1_1 or DCIformat 0_1 for unpaired spectrum operation during the interval.

In an example, if a UE is configured for a secondary cell with higherlayer parameter Default-DL-BWP indicating a default DL BWP among theconfigured DL BWPs and the UE is configured with higher layer parameterbwp-InactivityTimer indicating a timer value, the UE procedures on thesecondary cell may be same as on the primary cell using the timer valuefor the secondary cell and the default DL BWP for the secondary cell.

In an example, if a UE is configured by higher layer parameterActive-BWP-DL-SCell a first active DL BWP and by higher layer parameterActive-BWP-UL-SCell a first active UL BWP on a secondary cell orcarrier, the UE may use the indicated DL BWP and the indicated UL BWP onthe secondary cell as the respective first active DL BWP and firstactive UL BWP on the secondary cell or carrier.

In an example, a set of PDCCH candidates for a wireless device tomonitor is defined in terms of PDCCH search space sets. A search spaceset comprises a CSS set or a USS set. A wireless device monitors PDCCHcandidates in one or more of the following search spaces sets: aType0-PDCCH CSS set configured by pdcch-ConfigSIB1 in MIB or bysearchSpaceSIB1 in PDCCH-ConfigCommon or by searchSpaceZero inPDCCH-ConfigCommon for a DCI format with CRC scrambled by a SI-RNTI onthe primary cell of the MCG, a Type0A-PDCCH CSS set configured bysearchSpaceOtherSystemlnformation in PDCCH-ConfigCommon for a DCI formatwith CRC scrambled by a SI-RNTI on the primary cell of the MCG, aType1-PDCCH CSS set configured by ra-SearchSpace in PDCCH-ConfigCommonfor a DCI format with CRC scrambled by a RA-RNTI or a TC-RNTI on theprimary cell, a Type2-PDCCH CSS set configured by pagingSearchSpace inPDCCH-ConfigCommon for a DCI format with CRC scrambled by a P-RNTI onthe primary cell of the MCG, a Type3-PDCCH CSS set configured bySearchSpace in PDCCH-Config with searchSpaceType = common for DCIformats with CRC scrambled by INT-RNTI, SFI-RNTI, TPC-PUSCH-RNTI,TPC-PUCCH-RNTI, or TPC-SRS-RNTI and, only for the primary cell, C-RNTI,MCS-C-RNTI, or CS-RNTI(s), and a USS set configured by SearchSpace inPDCCH-Config with searchSpaceType = ue-Specific for DCI formats with CRCscrambled by C-RNTI, MCS-C-RNTI, SP-CSI-RNTI, or CS-RNTI(s).

In an example, a wireless device determines a PDCCH monitoring occasionon an active DL BWP based on one or more PDCCH configuration parameterscomprising: a PDCCH monitoring periodicity, a PDCCH monitoring offset,and a PDCCH monitoring pattern within a slot. For a search space set (SSs), the wireless device determines that a PDCCH monitoring occasion(s)exists in a slot with number

n_(s,f)^(μ)

in a frame with number n_(f) if

(n_(f) ⋅ N_(slot)^(frame,μ) + n_(s,f)^(μ) − o_(s))modk_(s) = 0.N_(slot)^(frame,μ)

is a number of slot in a frame when numerology µ is configured. o_(s) isa slot offset indicated in the PDCCH configuration parameters. k_(s) isa PDCCH monitoring periodicity indicated in the PDCCH configurationparameters. The wireless device monitors PDCCH candidates for the searchspace set for T_(s) consecutive slots, starting from slot

n_(s,f)^(μ),

and does not monitor PDCCH candidates for search space set s for thenext k_(s) - T_(s) consecutive slots. In an example, a USS at CCEaggregation level L ∈ {1, 2, 4, 8, 16} is defined by a set of PDCCHcandidates for CCE aggregation level L. If a wireless device isconfigured with CrossCarrierSchedulingConfig for a serving cell, thecarrier indicator field value corresponds to the value indicated byCrossCarrierSchedulingConfig.

In an example, a wireless device decides, for a search space set sassociated with CORESET p, CCE indexes for aggregation level Lcorresponding to PDCCH candidate m_(s,nCI) of the search space set inslot

n_(s,f)^(μ)

for an active DL BWP of a serving cell corresponding to carrierindicator field value n_(CI) as

$\text{L} \cdot \left\{ \left( {\text{Y}_{\text{p,n}_{\text{s,f}}^{\mu}} + \left\lfloor \frac{\text{m}_{\text{s,n}_{\text{CI}}} \cdot \text{N}_{\text{CCE,p}}}{\text{L} \cdot \text{M}_{\text{s,max}}^{(\text{L})}} \right\rfloor +} \right) \right)$

$\begin{array}{l}{\left( {\left( \text{n}_{\text{CI}} \right){mod}\left\lfloor {\text{N}_{\text{CCE,p}}/\text{L}} \right\rfloor} \right\} + \text{i, where, Y}_{\text{p,n}_{\text{s,f}}^{\mu}} = 0\text{for any CSS; Y}_{\text{p,n}_{\text{s,f}}^{\mu}} =} \\\left( {\text{A}_{\text{p}} \cdot \text{Y}_{\text{p,n}_{\text{s,f}}^{\mu} - 1}} \right)\end{array}$

mod D for a USS, Y_(p,-1) = n_(RNTI) ≠ 0, A_(p) = 39827 for p mod 3 = 0,A_(p) = 39829 for p mod 3 = 1, A_(p) = 39839 for p mod 3 = 2, and D =65537; i = 0, ⋯, L - 1; N_(CCE,p) is the number of CCEs, numbered from 0to N_(CCE,p) - 1, in CORESET p; n_(CI) is the carrier indicator fieldvalue if the wireless device is configured with a carrier indicatorfield by CrossCarrierSchedulingConfig for the serving cell on whichPDCCH is monitored; otherwise, including for any CSS,

n_(CI) = 0; m_(s,n_(CI)) = 0, …, M_(s,n_(CI))^((L)) − 1, where M_(s,n_(CI))^((L))

is the number of PDCCH candidates the wireless device is configured tomonitor for aggregation level L of a search space set s for a servingcell corresponding to n_(CI); for any CSS,

M_(s,max)^((L)) = M_(s,0)^((L)); for a USS, M_(s,max)^((L))

is the maximum of

M_(s,n_(CI))^((L))

over all configured n_(CI) values for a CCE aggregation level L ofsearch space set s; and the RNTI value used for n_(RNTI) is the C-RNTI.

In an example, DRX operation may be used by a UE to improve UE batterylifetime. With DRX configured, UE may discontinuously monitor downlinkcontrol channel, e.g., PDCCH or EPDCCH. A base station may configure DRXoperation with a set of DRX parameters, e.g., using RRC configuration.The set of DRX parameters may be selected based on the application typesuch that the wireless device may reduce power and resource consumption.In response to DRX being configured/activated, a UE may receive datapackets with an extended delay, since the UE may be in DRX Sleep/Offstate at the time of data arrival at the UE and the base station maywait until the UE transitions to the DRX ON state.

In an example, during a DRX mode, the UE may power down most of itscircuitry when there are no packets to be received. The UE may monitorPDCCH discontinuously in the DRX mode. The UE may monitor the PDCCHcontinuously when a DRX operation is not configured. During this timethe UE listens to the downlink (DL) (or monitors PDCCHs) which is calledDRX Active state. In a DRX mode, a time during which UE doesn’tlisten/monitor PDCCH is called DRX Sleep state.

FIG. 24 shows an example of the embodiment. A gNB may transmit an RRCmessage comprising one or more DRX parameters of a DRX cycle. The one ormore parameters may comprise a first parameter and/or a secondparameter. The first parameter may indicate a first time value of theDRX Active state (e.g., DRX On duration) of the DRX cycle. The secondparameter may indicate a second time of the DRX Sleep state (e.g., DRXOff duration) of the DRX cycle. The one or more parameters may furthercomprise a time duration of the DRX cycle. During the DRX Active state,the UE may monitor PDCCHs for detecting one or more DCIs on a servingcell. During the DRX Sleep state, the UE may stop monitoring PDCCHs onthe serving cell. When multiple cells are in active state, the UE maymonitor all PDCCHs on (or for) the multiple cells during the DRX Activestate. During the DRX off duration, the UE may stop monitoring all PDCCHon (or for) the multiple cells. The UE may repeat the DRX operationsaccording to the one or more DRX parameters.

In an example, DRX may be beneficial to the base station. In an example,if DRX is not configured, the wireless device may be transmittingperiodic CSI and/or SRS frequently (e.g., based on the configuration).With DRX, during DRX OFF periods, the UE may not transmit periodic CSIand/or SRS. The base station may assign these resources to the other UEsto improve resource utilization efficiency.

In an example, the MAC entity may be configured by RRC with a DRXfunctionality that controls the UE’s downlink control channel (e.g.,PDCCH) monitoring activity for a plurality of RNTIs for the MAC entity.The plurality of RNTIs may comprise at least one of: C-RNTI; CS-RNTI;INT-RNTI; SP-CSI-RNTI; SFI-RNTI; TPC-PUCCH-RNTI; TPC-PUSCH-RNTI;Semi-Persistent Scheduling C-RNTI; eIMTA-RNTI; SL-RNTI; SL-V-RNTI;CC-RNTI; or SRS-TPC-RNTI. In an example, in response to being inRRC_CONNECTED, if DRX is configured, the MAC entity may monitor thePDCCH discontinuously using the DRX operation; otherwise the MAC entitymay monitor the PDCCH continuously.

In an example, RRC may control DRX operation by configuring a pluralityof timers. The plurality of timers may comprise: a DRX On duration timer(e.g., drx-onDurationTimer); a DRX inactivity timer (e.g.,drx-InactivityTimer); a downlink DRX HARQ RTT timer (e.g.,drx-HARQ-RTT-TimerDL); an uplink DRX HARQ RTT Timer (e.g.,drx-HARQ-RTT-TimerUL); a downlink retransmission timer (e.g.,drx-RetransmissionTimerDL); an uplink retransmission timer (e.g.,drx-RetransmissionTimerUL); one or more parameters of a short DRXconfiguration (e.g., drx-ShortCycle and/or drx-ShortCycleTimer)) and oneor more parameters of a long DRX configuration (e.g., drx-LongCycle). Inan example, time granularity for DRX timers may be in terms of PDCCHsubframes (e.g., indicated as psf in the DRX configurations), or interms of milliseconds.

In an example, in response to a DRX cycle being configured, the ActiveTime may include the time while at least one timer is running. The atleast one timer may comprise drx-onDurationTimer, drx-InactivityTimer,drx-RetransmissionTimerDL, drx-RetransmissionTimerUL, ormac-ContentionResolutionTimer.

In an example, drx-inactivity-Timer may specify a time duration forwhich the UE may be active after successfully decoding a PDCCHindicating a new transmission (UL or DL or SL). This timer may berestarted upon receiving PDCCH for a new transmission (UL or DL or SL).The UE may transition to a DRX mode (e.g., using a short DRX cycle or along DRX cycle) in response to the expiry of this timer. In an example,drx-ShortCycle may be a first type of DRX cycle (e.g., if configured)that needs to be followed when UE enters DRX mode. In an example, aDRX-Config IE indicates the length of the short cycle.drx-ShortCycleTimer may be expressed as multiples of shortDRX-Cycle. Thetimer may indicate the number of initial DRX cycles to follow the shortDRX cycle before entering the long DRX cycle. drx-onDurationTimer mayspecify the time duration at the beginning of a DRX Cycle (e.g., DRXON). drx-onDurationTimer may indicate the time duration before enteringthe sleep mode (DRX OFF). drx-HARQ-RTT-TimerDL may specify a minimumduration from the time new transmission is received and before the UEmay expect a retransmission of a same packet. This timer may be fixedand may not be configured by RRC. drx-RetransmissionTimerDL may indicatea maximum duration for which UE may be monitoring PDCCH when aretransmission from the eNodeB is expected by the UE.

In response to a DRX cycle being configured, the Active Time maycomprise the time while a Scheduling Request is sent on PUCCH and ispending. In an example, in response to a DRX cycle being configured, theActive Time may comprise the time while an uplink grant for a pendingHARQ retransmission can occur and there is data in the correspondingHARQ buffer for synchronous HARQ process. In response to a DRX cyclebeing configured, the Active Time may comprise the time while a PDCCHindicating a new transmission addressed to the C-RNTI of the MAC entityhas not been received after successful reception of a Random AccessResponse for the preamble not selected by the MAC entity.

A DL HARQ RTT Timer may expire in a subframe and the data of thecorresponding HARQ process may not be successfully decoded. The MACentity may start the drx-RetransmissionTimerDL for the correspondingHARQ process. An UL HARQ RTT Timer may expire in a subframe. The MACentity may start the drx-RetransmissionTimerUL for the correspondingHARQ process. A DRX Command MAC control element or a Long DRX CommandMAC control element may be received. The MAC entity may stopdrx-onDurationTimer and stop drx-InactivityTimer. In an example,drx-InactivityTimer may expire or a DRX Command MAC control element maybe received in a subframe. In an example, in response to Short DRX cyclebeing configured, the MAC entity may start or restartdrx-ShortCycleTimer and may use Short DRX Cycle. Otherwise, the MACentity may use the Long DRX cycle.

In an example, drx-ShortCycleTimer may expire in a subframe. The MACentity may use the Long DRX cycle. In an example, a Long DRX Command MACcontrol element may be received. The MAC entity may stopdrx-ShortCycleTimer and may use the Long DRX cycle.

In an example, if the Short DRX Cycle is used and [(SFN * 10) + subframenumber] modulo (drx-ShortCycle) = (drxStartOffset) modulo(drx-ShortCycle), the wireless device may start drx-onDurationTimer. Inan example, if the Long DRX Cycle is used and [(SFN * 10) + subframenumber] modulo (drx-longCycle) = drxStartOffset, the wireless device maystart drx-onDurationTimer.

FIG. 25 shows example of DRX operation. A base station may transmit anRRC message comprising configuration parameters of DRX operation. A basestation may transmit a DCI for downlink resource allocation via a PDCCH,to a UE. the UE may start the drx-lnactivityTimer during which, the UEmay monitor the PDCCH. After receiving a transmission block (TB) whenthe drx-lnactivityTimer is running, the UE may start a HARQ RTT Timer(e.g., drx-HARQ-RTT-TimerDL), during which, the UE may stop monitoringthe PDCCH. The UE may transmit a NACK to the base station uponunsuccessful receiving the TB. When the HARQ RTT Timer expires, the UEmay monitor the PDCCH and start a HARQ retransmission timer (e.g.,drx-RetransmissionTimerDL). When the HARQ retransmission timer isrunning, the UE may receive a second DCI indicating a DL grant for theretransmission of the TB. If not receiving the second DCI before theHARQ retransmission timer expires, the UE may stop monitoring the PDCCH.

FIG. 26A show example of a power saving mechanism based on wake-up. AgNB may transmit one or more messages comprising parameters of a wake-upduration (e.g., a power saving duration, or a Power Saving Channel(PSCH) occasion), to a UE. The wake-up duration may be located a numberof slots (or symbols) before a DRX On duration of a DRX cycle. Thenumber of slots (or symbols), or, referred to as a gap between a wakeupduration and a DRX on duration, may be configured in the one or more RRCmessages or predefined as a fixed value. The gap may be used for atleast one of: synchronization with the gNB; measuring reference signals;and/or retuning RF parameters. The gap may be determined based on acapability of the UE and/or the gNB. In an example, the parameters ofthe wake-up duration may be pre-defined without RRC configuration. In anexample, the wake-up mechanism may be based on a wake-up indication viaa PSCH. The parameters of the wake-up duration may comprise at least oneof: a PSCH channel format (e.g., numerology, DCI format, PDCCH format);a periodicity of the PSCH; a control resource set and/or a search spaceof the PSCH. When configured with the parameters of the wake-upduration, the UE may monitor the wake-up signal or the PSCH during thewake-up duration. When configured with the parameters of the PSCHoccasion, the UE may monitor the PSCH for detecting a wake-up indicationduring the PSCH occasion. In response to receiving the wake-upsignal/channel (or a wake-up indication via the PSCH), the UE maywake-up to monitor PDCCHs according to the DRX configuration. In anexample, in response to receiving the wake-up indication via the PSCH,the UE may monitor PDCCHs in the DRX active time (e.g., whendrx-onDurationTimer is running). The UE may go back to sleep if notreceiving PDCCHs in the DRX active time. The UE may keep in sleep duringthe DRX off duration of the DRX cycle. In an example, if the UE doesn’treceive the wake-up signal/channel (or a wake-up indication via thePSCH) during the wake-up duration (or the PSCH occasion), the UE mayskip monitoring PDCCHs in the DRX active time.

In an example, a power saving mechanism may be based on a go-to-sleepindication via a PSCH. FIG. 26B shows an example of a power saving basedon go-to-sleep indication. In response to receiving a go-to-sleepindication via the PSCH, the UE may go back to sleep and skip monitoringPDCCHs during the DRX active time (e.g., next DRX on duration of a DRXcycle). In an example, if the UE doesn’t receive the go-to-sleepindication via the PSCH during the wake-up duration, the UE monitorsPDCCHs during the DRX active time, according to the configurationparameters of the DRX operation. This mechanism may reduce powerconsumption for PDCCH monitoring during the DRX active time.

In an example, a power saving mechanism may be implemented by combiningFIG. 26A and FIG. 26B. A base station may transmit a power savingindication, in a DCI via a PSCH, indicating whether the wireless deviceshall wake up for next DRX on duration or skip next DRX on duration. Thewireless device may receive the DCI via the PSCH. In response to thepower saving indication indicating the wireless device shall wake up fornext DRX on duration, the wireless device may wake up for next DRX onduration. The wireless device monitors PDCCH in the next DRX on durationin response to the waking up. In response to the power saving indicationindicating the wireless device shall skip (or go to sleep) for next DRXon duration, the wireless device goes to sleep or skip for next DRX onduration. The wireless device skips monitoring PDCCH in the next DRX onduration in response to the power saving indication indicating thewireless device shall go to sleep for next DRX on duration.

FIG. 27 shows an example embodiment of power saving mechanism. A basestation (e.g., gNB) may transmit to a wireless device (e.g., UE), one ormore RRC messages comprising first configuration parameters of a powersaving channel (PSCH) and second configuration parameters of a powersaving (PS) operation. The first configuration parameters of the PSCHmay comprise at least one of: one or more first search spaces (SSs)and/or one or more first control resource sets (COREST) on which the UEmonitors the PSCH, one or more first DCI formats with which the UEmonitors the PSCH, a radio network temporary identifier (RNTI) dedicatedfor monitoring the PSCH (e.g., PS-RNTI different from 3GPP existing RNTIvalues configured for the wireless device). The second configurationparameters of the PS operation may comprise at least one of: one or moresecond SSs and/or one or more second CORESTs on which the UE monitorsPDCCHs in the PS operation, one or more first DCI formats with which theUE monitors PDCCHs in the PS operation, one or more MIMO parametersindicating a first maximum number of antenna (layers, ports, TRPs,panels, and/or the like) based on which the UE perform MIMO processing(transmission or reception) in the PS operation, one or more firstcross-slot scheduling indicator indicating whether cross-slot schedulingis configured or not when the UE is in the PS operation, a BWP indexindicating on which the UE transmit or receive data packet in the PSoperation, and/or a cell index indicating on which the UE transmit orreceive data packet in the PS operation. The one or more RRC messagesmay further comprise third configuration parameters of a normal functionoperation (e.g., full function, non-PS, or the like). The thirdconfiguration parameters may comprise at least one of: one or more thirdSSs and/or one or more third CORESTs on which the UE monitors PDCCHs inthe non-PS operation, one or more second DCI formats with which the UEmonitors PDCCHs in the non-PS operation, one or more MIMO parametersindicating a second maximum number of antenna (layers, ports, TRPs,panels, and/or the like) based on which the UE perform MIMO processing(transmission or reception) in the non-PS operation, one or more secondcross-slot scheduling indicator indicating whether cross-slot schedulingis configured or not when the UE is in the non-PS operation, and/or thelike. The UE, based on cross-slot scheduling being configured, mayswitch off some receiver modules (e.g., data buffering, RF chain,channel tracking, etc.) after receiving a DCI indicating a cross-slotscheduling and before receiving a data packet based on the DCI, for thepurpose of power saving. In an example, the one or more second SSsand/or the one or more second CORESTs may occupy smaller radio resourcesthan the one or more third SSs and/or the one or more third CORESTs,e.g., for the purpose of power saving. The first maximum number may besmaller than the second maximum number, e.g., for the purpose of powersaving.

As shown in FIG. 27 , when configured with the parameters of the PSCHand PS operation, the UE may monitor the PSCH (e.g., on the 1stSS/CORESET) for detecting a DCI with CRC scrambled by the PS-RNTI duringthe PSCH monitoring occasions. Based on the PSCH monitoring, the UE maydetect a PS indication contained in the DCI received via the PSCH. TheDCI may further indicate an active BWP switching. In response toreceiving the PS indication via the PSCH, the UE may start performing aPS operation based on the one or more second configuration parameters ofthe PS operation. Performing a PS operation based on the one or moresecond configuration parameters may comprise at least one of: monitoringPDCCHs on 2nd PDCCH occasions and on 2nd SSs/CORESETs, refraining frommonitoring the PSCH on 1st SSs/CORESETs, refraining from monitoringPDCCHs on 3rd PDCCH occasions and on 3rd SSs/CORESETs, transmitting orreceiving data packets with the 1st maximum number of antenna (layers,ports, TRPs, panels, and/or the like), and/or transmitting or receivingdata packets with cross-slot scheduling based on the one or more firstcross-slot scheduling indicator. Performing the PS operation may furthercomprise switching an active BWP of one or more cells (e.g., aPCell/SCell, or a cell group) to a dormant BWP of the one or more cells.The UE may monitor the PDCCHs on 2nd PDCCH occasions and on 2ndSSs/CORESETs continuously when DRX operation is not configured. The UEmay monitor the PDCCHs on 2nd PDCCH occasions and on 2nd SSs/CORESETsdiscontinuously in a DRX active time (e.g., next DRX on duration) whenDRX operation is configured. The UE, based on the monitoring the PDCCHon 2nd PDCCH occasions, may transmit or receive data packets or TBs inresponse to receiving a DCI indicating an uplink grant or a downlinkassignment.

In an example, in response to receiving the PS indication via the PSCH,the UE may transition a SCell from an active state to a dormant state,based on the PS indication indicating a state transition of the SCell. Adormant state of a SCell may be a time period duration which thewireless device may: stop monitoring PDCCH(s) on/for the SCell, stopreceiving PDSCH(s) on the SCell, stop transmitting uplink signals(PUSCH, PUCCH, PRACH, DMRS, and/or PRACH) on the SCell, and/or transmitCSI report for the SCell. The wireless device may maintain the dormantstate of the SCell until receiving a second indicator indicating atransition of the SCell from the dormant state to the active state.

As shown in FIG. 27 , when configured with the parameters of the PSCHand PS operation, the UE may monitor the PSCH (e.g., on the 1stSS/CORESET) during the PSCH monitoring occasions. The UE may not detecta PS indication via the PSCH, e.g., when a base station determines thatthe UE shall stay in a full function mode, or a non-PS mode. In responseto not receiving the PS indication via the PSCH, the UE may startperforming operations in a full function mode based on the one or morethird configuration parameters. In an example, a base station maytransmit a PS indication indicating whether the wireless device shallstay in a full function mode. The wireless device may receive the PSindication via a PSCH. In response to the PS indication indicating thewireless shall stay in a full function mode, the wireless device maystart performing operations in the full function mode based on the oneor more third configuration parameters.

In an example, performing operations in a full function mode based onthe one or more third configuration parameters may comprise at least oneof: monitoring PDCCHs on 3rd PDCCH occasions and on 3rd SSs/CORESETs,refraining from monitoring the PSCH on 1st SSs/CORESETs, refraining frommonitoring PDCCHs on 2nd PDCCH occasions and on 2nd SSs/CORESETs,transmitting or receiving data packets with the 2nd maximum number ofantenna (layers, ports, TRPs, panels, and/or the like), transmitting orreceiving data packets with same-slot scheduling based on the one ormore second cross-slot scheduling indicator indicating same-slotscheduling is configured. The UE may monitor the PDCCHs on 3rd PDCCHoccasions and on 3rd SSs/CORESETs continuously when DRX operation is notconfigured. The UE may monitor the PDCCHs on 3rd PDCCH occasions and on3rd SSs/CORESETs discontinuously in a DRX active time when DRX operationis configured. The UE, based on the monitoring the PDCCH on 3rd PDCCHoccasions, may transmit or receive data packets or TBs in response toreceiving a DCI indicating an uplink grant or a downlink assignment.

FIG. 28 shows an example of a downlink beam failure recovery (BFR)procedure of a cell. In an example, a wireless device may receive, froma base station, one or more messages at time T0. The one or moremessages may comprise one or more configuration parameters for aplurality of cells. The plurality of cells may comprise a first cell(e.g., PCell, PSCell, PUCCH SCell, SCell) and one or more secondarycells. The one or more secondary cells may comprise a second cell (e.g.,SCell, SCell configured with PUCCH). The one or more messages maycomprise one or more RRC messages (e.g. RRC connection reconfigurationmessage, or RRC connection reestablishment message, or RRC connectionsetup message). The one or more configuration parameters may indicatecell-specific indices (e.g., provided by a higher layer parameterservCellIndex) for the plurality of cells. In an example, each cell ofthe plurality of cells may be identified by a respective onecell-specific index of the cell-specific indices.

In an example, the one or more configuration parameters may comprise BWPconfiguration parameters for a plurality of BWPs. The plurality of BWPsmay comprise a first plurality of DL BWPs of a cell and/or a firstplurality of UL BWPs of the cell. The one or more configurationparameters may further comprise BWP specific indices for the pluralityof BWPs. In an example, each BWP of the plurality of BWPs may beidentified by a respective one BWP specific index of the BWP specificindices (e.g., provided by a higher layer parameter bwp-ID in the one ormore configuration parameters).

In an example, the one or more configuration parameters may indicate oneor more first RSs (e.g., RadioLinkMonitoringRS provided in an IERadioLinkMonitoringConfig) for a downlink BWP of the second cell (e.g.,explicit BFD configuration). At least one RS of the one or more firstRSs may be transmitted/configured on/in the first cell, and/or thesecond cell. The second cell and the first cell may share the at leastone RS based on operating in intra-band and/or QCL-ed (e.g.,cross-carrier QCL) and/or based on sharing similar channelcharacteristics (e.g., Doppler spread, spatial filter, etc.). The one ormore configuration parameters may indicate a maximum beam failureinstance (BFI) counter (e.g., beamFailurelnstanceMaxCount). The wirelessdevice may assess the one or more first RSs to detect a beam failure forthe downlink BWP of the second cell. The one or more configurationparameters may indicate a first threshold (e.g., provided byrlmInSyncOutOfSyncThreshold, Qout,LR). The one or more configurationparameters may indicate one or more second RSs (e.g.,candidateBeamRSList provided in IE BeamFailureRecoveryConfig). Thewireless device may assess the one or more second RSs to select acandidate RS among the one or more second RSs for a BFR procedure of thedownlink BWP of the second cell. The one or more second RSs may compriseone or more second CSI-RSs, and/or one or more second SS/PBCH blocks.

In an example, the one or more configuration parameters may indicate asecond threshold (e.g., provided by rsrp-ThresholdSSB in the IEBeamFailureRecoveryConfig) for a BFR procedure. The wireless device mayuse the second threshold in a candidate beam selection of the secondcell. The one or more configuration parameters may indicate a BFR timer(e.g., provided by beamFailureRecoveryTimer in the IEBeamFailureRecoveryConfig) for a BFR of the second cell (or the downlinkBWP).

In an example, the one or more configuration parameters may indicate asearch space set (e.g., provided by recoverySearchSpacelD in the IEBeamFailureRecoveryConfig). The search space set may belinked/associated with a CORESET. The search space set may indicate theCORESET. The wireless device may monitor the CORESET for a BFR procedureof the second cell (or of the downlink BWP). The base station mayconfigure the CORESET on the first cell. The base station may configurethe CORESET on the second cell. The wireless device may monitor thesearch space set (e.g., linked to the CORESET) for a BFR procedure ofthe downlink BWP. The downlink BWP may be an active downlink BWP of thesecond cell. A physical layer in the wireless device may assess a firstradio link quality of the one or more first RSs (for a beam failuredetection of the downlink BWP). The physical layer may provide a BFIindication to a higher layer (e.g. MAC) of the wireless device when thefirst radio link quality is worse (e.g., higher BLER, lower L1-RSRP,lower L1-SINR) than the first threshold.

In an example, the higher layer (e.g., MAC) of the wireless device mayincrement BFI_COUNTER by one in response to the physical layer providingthe BFI indication. The BFI_COUNTER may be a counter for a BFIindication. The wireless device may initially set the BFI_COUNTER tozero. Based on the incrementing the BFI_COUNTER, the BFI_COUNTER may beequal to or greater than the maximum BFI counter (e.g.,beamFailurelnstanceMaxCount). The wireless device may detect a beamfailure of the downlink BWP of the second cell based on the BFI_COUNTERbeing equal to or greater than the maximum BFI counter. The wirelessdevice may initiate a BFR procedure for the downlink BWP of the secondcell based on the detecting the beam failure of the downlink BWP. Basedon the initiating the BFR procedure, the wireless device may start theBFR timer.

In an example, based on the initiating the BFR procedure, the wirelessdevice may initiate a candidate beam selection for the BFR procedure.The candidate beam selection may comprise selecting/identifying acandidate RS (e.g., CSI-RS, SS/PBCH blocks) in/among the one or moresecond RSs (with quality higher than the second threshold). Theinitiating the candidate beam selection may comprise requesting, by thehigher layer from the physical layer, one or more indices (of theRS-specific indices) associated with one or more candidate RSs among theone or more second RSs and/or one or more candidate measurements (e.g.,L1-RSRP measurements) of the one or more candidate RSs. The physicallayer of the wireless device may perform one or more measurements (e.g.L1-RSRP measurement) for the one or more second RSs. The wireless devicemay determine that the one or more candidate measurements, of the one ormore measurements, of the one or more candidate RSs, are better (e.g.lower BLER or higher L1-RSRP or higher SINR) than the second threshold(e.g., rsrp-ThresholdSSB). Based on a request, by the higher layer fromthe physical layer, the physical layer may provide the first measurementand a first RS-specific index of the first RS and the second measurementand a second RS-specific index of the second RS.

In an example, the one or more configuration parameters may indicateuplink physical channels (e.g., PUCCH, PRACH, PUSCH). The uplinkphysical channels may comprise physical random-access channels (PRACH)resources, physical uplink control channel (PUCCH) resources, and/orphysical uplink shared channel (PUSCH) resources.

In an example, the wireless device may transmit, at time T2 in FIG. 28 ,an uplink signal (e.g., preamble via PRACH, beam failure recoveryrequest (BFRQ) transmission via PUCCH, scheduling request (SR) viaPUCCH, MAC-CE via PUSCH, aperiodic CSI-RS via PUSCH) via at least oneuplink physical channel (e.g., PRACH or PUCCH or PUSCH) of the uplinkphysical channels based on initiating the BFR procedure for the secondcell.

In an example, the wireless device may receive a DCI from the basestation at time T3 in FIG. 28 . The DCI may indicate uplink/downlinkfrequency/time resources for downlink assignment/uplink grant. The DCImay trigger a CSI report (e.g., aperiodic CSI report). The DCI maycomprise a CSI request field triggering the CSI report.

In an example, the wireless device may transmit a second uplink signal(e.g., PUSCH, transport block, aperiodic CSI-report, UCI, PUCCH, MAC-CE,etc.) via uplink resources indicated by the DCI at time T4. The seconduplink signal may be a MAC-CE (e.g., BFR MAC-CE, PHR MAC-CE, BSR, andthe like). The second uplink signal may be a layer-1 report. In anexample, the second uplink signal may be a CSI report (e.g., aperiodicCSI report). The second uplink signal may comprise/indicate the secondcell-specific index of the second cell.

In an example, the wireless device may select/identify a candidate RS(of the one or more second RSs) associated/identified with a candidateRS index of the RS-specific indices for the BFR procedure. Based onselecting/identifying the candidate RS, the second uplink signal mayindicate the candidate RS index of the candidate RS.

In an example, the wireless device may skip transmitting the BFRQ attime T2 and skip receiving the DCI at time T3, for the BFR procedure ofthe SCell. The wireless device may skip transmitting the BFRQ and skipreceiving the DCI when there is available uplink grant for transmittingthe second uplink signal indicating the candidate RS index/cell index.The wireless device may transmit the second uplink signal (e.g., a MACCE) via the available uplink grant (e.g., dynamic grant or configuredgrant) in response to initiating the BFR procedure.

In an example, when performing a BFR procedure for a SCell as shown inFIG. 28 , a wireless device may not identify a candidate RS (or acandidate beam identified by the candidate RS), from a plurality ofcandidate RSs, has a lower BLER or higher L1-RSRP or higher SINR thanthe second threshold (e.g., rsrp-ThresholdSSB). In existingtechnologies, in response to transmitting a signal (e.g., a MAC CE)indicating no candidate RS is identified, the wireless device maydeactivate the SCell. In existing technologies, in response totransmitting a signal (e.g., a MAC CE) indicating no candidate RS isidentified, the wireless device may continue monitoring the PDCCH of theSCell and maintain the active state of the SCell. Deactivating theSCell, in case of no candidate beam being identified, may cause SCellreactivation delay. In an example, a base station may transmit a MAC CEindicating an activation of the SCell after a beam pair link on theSCell between a base station and the wireless device is recovered.Delivery of the MAC CE may comprise: transmitting from a base station aDCI for scheduling the MAC CE, transmitting from a base station the MACCE based on the DCI, receiving by the wireless device the DCI, receivingby the wireless device the MAC CE, transmitting by the wireless deviceHARQ-ACK for the reception of the MAC CE, retransmitting by the basestation the MAC CE if the HARQ-ACK indicates a NACK for the MAC CE. Awireless device, by maintaining the SCell in active state in case of nocandidate beam being identified, may increase power consumption, e.g.,for PDCCH monitoring on the SCell, uplink transmission on the SCell. Themonitoring the PDCCH on the SCell, or the uplink transmission on theSCell, when a BFR procedure is initiated and no candidate beam isidentified, may not be successful and increase uplink interference toother wireless devices. There is a need to improve BFR procedure for aSCell, e.g., when no candidate beam is identified for the BFR procedure.Embodiments of present disclosure may reduce activation/reactivationlatency of a SCell, power consumption of a wireless device, uplinkinterference to other wireless devices, for a BFR procedure on theSCell.

FIG. 29 shows an example embodiment of BFR procedure on a SCell. Asshown in FIG. 29 , a base station may transmit to a wireless device, oneor more RRC messages comprising configuration parameters of a pluralityof cells comprising a SCell. The one or more RRC messages comprise aserving cell configuration IE (e.g., ServingCellConfig) used toconfigure (add or modify) the wireless device with a serving cell. Theserving cell may be a SpCell or an SCell of an MCG or SCG. Theconfiguration parameters of the SCell may comprise first configurationparameters of a BFR procedure on the SCell, the first configurationparameters indicating a first plurality of RSs for beam failuredetection, a second plurality of RSs for candidate beam identification,a first threshold for beam failure detection, a second threshold forcandidate beam identification. The configuration parameters of the SCellmay further indicate a plurality of search spaces, a plurality ofCORESETs for PDCCH monitoring on the SCell.

As shown in FIG. 29 , a base station may transmit a command (e.g., aDCI, a MAC CE, and/or an RRC message) indicating an activation of theSCell. In response to receiving the command, the wireless deviceactivates the SCell to an active state. When the SCell is in activestate, the wireless device may: monitor PDCCH(s) on the plurality ofsearch spaces of the plurality of CORESETs on an active BWP of theSCell, receive PDSCH via the active BWP of the SCell, transmitPUCCH/PUSCH/SRS/PRACH via an uplink active BWP of the SCell. In responseto the SCell being in active state, the wireless device may perform aBFR procedure based on monitoring the first plurality of RSs and thefirst threshold for beam failure detection. The wireless device mayperform the beam failure detection by implementing examples of FIG. 28 .

As shown in FIG. 29 , the wireless device may perform a candidate beamselection from the second plurality of RSs for the BFR procedure on theSCell. The wireless device may perform the candidate beam selection byimplementing examples of FIG. 28 . The wireless device may not identifya candidate beam, from the second plurality of RSs, having a lower BLERor higher L1-RSRP or higher SINR than the second threshold (e.g.,rsrp-ThresholdSSB).

In response to no candidate beam being identified, the wireless devicetransmits a MAC CE indicating no candidate beam identified on the SCell.In an example, based on no candidate beam being identified, the wirelessdevice may transition the SCell from the active state to a dormant state(a power saving state). When the SCell is transitioned into the dormantstate, the wireless device may: stop monitoring the PDCCH(s) on theplurality of search spaces of the plurality of CORESETs on the SCell,stop receiving PDSCH via the SCell, stop transmittingPUCCH/PUSCH/SRS/PRACH via the SCell. In response to transitioning theSCell into dormant state, the wireless device may transmit CSI reportfor the SCell (e.g., on a PCell or a PUCCH SCell). The wireless devicemay transmit the CSI report, for the SCell in the dormant state, with areduced transmission periodicity, with a less quantity of CSI reportcontents, and/or on a smaller PUCCH resource, compared with CSI reportfor the SCell in the active state. In response to transitioning theSCell into dormant state, the wireless device may reduce PDCCHmonitoring on the SCell, compared with PDCCH monitoring on the SCell inthe active state. The wireless device may, in response to transitioningthe SCell into dormant state, monitor PDCCH: with reduced monitoringperiodicity, with reduced number of search spaces, with reduced numberof CORESETs, and/or with reduced DCI formats, compared with PDCCHmonitoring on the SCell in the active state.

As shown in FIG. 29 , based on receiving the CSI report for the SCell inthe dormant state, the base station may determine to transition theSCell from the dormant state to the active state. The base station maydetermine to transition the SCell to the active state when the CSIreport (e.g., comprising beam reports) indicates the beam quality of abeam pair link on the SCell between the base station and the wirelessdevice becomes better than a threshold. In response to the CSI reportindicating the beam quality is better than the threshold, the basestation may transmit a DCI indicating a transition of the SCell from thedormant state to the active state. A transition, based on the DCI,between the SCell dormant state and the SCell active state, may reduceactivation delay for the SCell when a BFR procedure is initiated and nocandidate beam is identified. Example embodiments may reduce powerconsumption of the wireless device for PDCCH monitoring on the SCellwhen a BFR procedure is initiated and no candidate beam is identified.Example embodiments may reduce uplink interference to other wirelessdevice when a BFR procedure is initiated and no candidate beam isidentified. Example embodiments may reduce SCell activation latency whena BFR procedure is initiated and no candidate beam is identified.

FIG. 30 shows an example flowchart of a BFR procedure on a SCell. Awireless device may receive one or more RRC messages comprisingconfiguration parameters of a SCell, the configuration parameterscomprising first configuration parameters of a BFR procedure on theSCell and second configuration parameters of a dormancy on the SCell. Inan example, the first configuration parameters may be implemented byexamples of FIG. 28 . The second configuration parameters may indicatePDCCH monitoring configurations for the dormant state and/or CSI reportconfigurations for the dormant state. The wireless device may receive acommand (e.g., a DCI, MAC CE and/or an RRC message) indicatingactivation of the SCell. In response to activation of the SCell, thewireless device may perform a BFR procedure based on the firstconfiguration parameters of the BFR procedure. The wireless device mayperform a candidate beam selection for the BFR procedure on the SCell,e.g., by implementing examples of FIG. 28 .

In an example, the wireless device may determine a candidate beam isidentified in response to channel quality of the candidate beam beingbetter than a threshold. In response to the candidate beam beingidentified, the wireless device may transmit a MAC CE indicating thecandidate beam for the SCell. In response to transmitting the MAC CEindicating the identified candidate beam, the wireless device maycontinue monitoring PDCCH(s) on the SCell and maintain an active stateof the SCell.

In an example, the wireless device may determine a candidate beam is notidentified in response to channel quality of the candidate beam notbeing better than a threshold. In response to the candidate beam notbeing identified, the wireless device may transmit a MAC CE indicatingno candidate beam for the SCell is identified. In response totransmitting the MAC CE indicating no candidate beam for the SCell isidentified, the wireless device may transition the SCell from the activestate to a dormant state. Based on the dormant state, the wirelessdevice may stop monitoring PDCCH(s) on the SCell and transmit CSI reportfor the SCell. Based on the dormant state, the wireless device mayreduce PDCCH(s) periodicity on the SCell, compared with PDCCH monitoringon the SCell in active state. Based on the dormant state, the wirelessdevice may transmit CSI report with reduced reporting periodicity forthe SCell, compared with CSI reporting on the SCell in active state.

In an example, a wireless device may transition a SCell from activestate to dormant state in response to receiving a command as a responseto a MAC CE, transmitted from the wireless device, indicating nocandidate beam is identified for a BFR on the SCell. FIG. 31 shows anexample embodiment of BFR procedure on a SCell. As shown in FIG. 31 , abase station may transmit to a wireless device, one or more RRC messagescomprising configuration parameters of a plurality of cells comprising aSCell. The one or more RRC messages may be implemented by examples ofFIG. 29 .

As shown in FIG. 31 , a base station may transmit a command (e.g., aDCI, a MAC CE, and/or an RRC message) indicating an activation of theSCell. In response to receiving the command, the wireless deviceactivates the SCell to an active state. In response to the SCell beingin active state, the wireless device may perform a BFR procedure basedon monitoring the first plurality of RSs and the first threshold forbeam failure detection. The wireless device may perform the beam failuredetection by implementing examples of FIG. 28 .

As shown in FIG. 31 , the wireless device may perform a candidate beamselection from the second plurality of RSs for the BFR procedure on theSCell. The wireless device may not identify a candidate beam, from thesecond plurality of RSs, having a lower BLER or higher L1-RSRP or higherSINR than the second threshold (e.g., rsrp-ThresholdSSB).

In response to no candidate beam being identified, the wireless devicetransmits a MAC CE indicating no candidate beam identified on the SCell.The wireless device may maintain an active state of the SCell inresponse to transmitting the MAC CE. The wireless device may continuemonitoring the PDCCH on the SCell, when the SCell is in active state.

In an example, the wireless device may receive a confirmation forreception of the MAC CE at the base station. The wireless device mayreceive a DCI comprising an uplink grant as a response to the MAC CE.The DCI, as a confirmation for the reception of the MAC CE, may indicatea new transmission for a HARQ process same as the one used fortransmission of the MAC CE. The DCI, by toggling an NDI value of an NDIfield of the DCI, may indicate the confirmation for the reception of theMAC CE. The DCI, as a confirmation for the reception of the MAC CE, maynot comprise a power saving indication, or a SCell dormancy indication.In response to receiving the DCI (e.g., or a confirmation of the MACCE), the wireless device may transition the SCell from the active stateto a dormant state (a power saving state). The wireless device may, whenthe SCell is transitioned into the dormant state: stop monitoring thePDCCH(s) on the plurality of search spaces of the plurality of CORESETson the SCell, stop receiving PDSCH via the SCell, stop transmittingPUCCH/PUSCH/SRS/PRACH via the SCell. In response to transitioning theSCell into dormant state, the wireless device may transmit CSI reportfor the SCell (e.g., on a PCell or a PUCCH SCell). The wireless devicemay transmit the CSI report, for the SCell in the dormant state, with areduced transmission periodicity, with a less quantity of CSI reportcontents, and/or on a smaller PUCCH resource, compared with CSI reportfor the SCell in the active state. In response to transitioning theSCell into dormant state, the wireless device may reduce PDCCHmonitoring on the SCell, compared with PDCCH monitoring on the SCell inthe active state. The wireless device may, in response to transitioningthe SCell into dormant state, monitor PDCCH: with reduced monitoringperiodicity, with reduced number of search spaces, with reduced numberof CORESETs, and/or with reduced DCI formats, compared with PDCCHmonitoring on the SCell in the active state. Example embodiments mayreduce power consumption of the wireless device for PDCCH monitoring onthe SCell when a BFR procedure is initiated and no candidate beam isidentified. Example embodiments may reduce SCell activation latency whena BFR procedure is initiated and no candidate beam is identified.

In an example, a wireless device may initiate a BFR procedure for afirst SCell and may not identify a candidate beam for the BFR procedurefor the first SCell, the first SCell being a PUCCH SCell. In response tono candidate beam being identified, the wireless device may maintain anactive state of the first SCell, and transition one or more secondSCells, configured with the first SCell as the PUCCH SCell of the one ormore second SCells, from active state to a dormant state.

FIG. 32 shows an example of BFR procedure on a SCell. In an example, awireless device may initiate a BFR procedure for a first SCell and maynot identify a candidate beam for the BFR procedure for the first SCell,the first SCell being a PUCCH SCell.

In an example, in response to no candidate beam being identified, thewireless device may clear PUCCH resources on the first SCell andmaintain the active state of the first SCell, if the PUCCH resources isconfigured on the first SCell. In an example, the wireless device mayclear the PUCCH resources in response to a beam correspondence existingbetween downlink and uplink. The beam correspondence between downlinkand uplink may exist when a wireless device determines a transmissionspatial domain filter for uplink signal (e.g., PUCCH/PUSCH/SRS/PRACH)based on (e.g., as same as) a reception spatial domain filter fordownlink signal (e.g., SSBs/CSI-RS/DMRS). Clearing the PUCCH resourcesmay comprise not maintaining configuration parameters of the PUCCHresources and stopping using the PUCCH resources. After clearing thePUCCH resources, the wireless device may receive an RRC message forPUCCH resource reconfiguration when the base station determines toreconfigure the PUCCH resource on the first SCell.

In an example, in response to no candidate beam being identified, thewireless device may suspend PUCCH transmission(s) on the first SCell andmaintain the active state of the first SCell, if the PUCCH resources isconfigured on the first SCell. The wireless device may suspend PUCCHtransmission(s) on the first SCell and maintain the active state of thefirst SCell, in response to a beam correspondence existing betweendownlink and uplink. Suspending the PUCCH transmission may comprisemaintaining configuration parameters of the PUCCH resources and stoppingtransmitting UCIs via the PUCCH resources. After suspending the PUCCHresources, the wireless device may resume PUCCH transmission (e.g.,without receiving a PUCCH resource reconfiguration RRC message) when abeam pair link is recovered.

In an example, a wireless device may initiate a BFR procedure for afirst SCell and may not identify a candidate beam for the BFR procedurefor the first SCell, the first SCell being a PUCCH SCell. In response toan uplink transmission configuration indicator (UL-TCI) indicating anSSB/CSI-RS index of the first SCell, the wireless device may suspendPUCCH/PUSCH transmission(s) on the first SCell and maintain the activestate of the first SCell. The SSB/CSI-RS index may identify one of aplurality of RSs configured on the first SCell for beam failuredetection, or candidate beam selection. Suspending the PUCCH/PUSCHtransmission may comprise maintaining configuration parameters of thePUCCH/PUSCH resources. After suspending the PUCCH/PUSCH resources, thewireless device may resume PUCCH/PUSCH transmission (e.g., withoutreceiving a PUCCH/PUSCH resource reconfiguration RRC message) when abeam pair link is recovered. In an example, the wireless device, whenthe UL-TCI indicates an SSB/CSI-RS index of a cell, may determine atransmission spatial domain filter based on a reception spatial domainfilter for an SSB/CSI-RS identified by the SSB/CSI-RS index. In anexample, the wireless device may receive the UL-TCI in a DCI indicatinguplink grant.

In an example, a wireless device may initiate a BFR procedure for afirst SCell and may not identify a candidate beam for the BFR procedurefor the first SCell. In response to no candidate beam being identified,the wireless device may suspend configured grant transmission, SP-CSItransmission on PUCCH/PUSCH, and/or SP-SRS transmission. Suspending theconfigured grant, SP-CSI, and/or SP-SRS transmission may comprise:maintaining configuration parameters of the configured grant, SP-CSIand/or the SP-SRS, and/or stopping transmitting the configured grant,SP-CSI and/or the SP-SRS. After suspending the transmissions (configuredgrant, SP-CSI or SP-SRS), the wireless device may resume thetransmission (e.g., without receiving activation command (a MAC CE or aDCI) indicating the activation of the transmissions) when a beam pairlink is recovered.

FIG. 33 shows a flowchart of SCell BFR procedure as per an aspect of anexample embodiment of the present disclosure. At 3310, a wireless devicemonitors a downlink control channel of a cell in an active state. At3320, the wireless device initiates a beam failure recovery (BFR)procedure in response to detecting a number of beam failure instances onthe cell. At 3330, the wireless device determines, in response to theinitiating the BFR procedure, no candidate beam is identified based on athreshold. At 3340, the wireless device transitions, in response to nocandidate beam being identified, the cell from the active state to adormancy. At 3350, the wireless device, based on the transitioning thecell to the dormancy, stops monitoring the downlink control channel onthe cell and/or transmits channel state information reports for adormant bandwidth part of the cell.

In an example, in response to no candidate beam being identified for abeam failure recovery procedure of a cell, a wireless device maytransition the cell to a dormancy while maintaining the cell activated.

According to an example embodiment, the transitioning the cell to thedormancy comprises stopping monitoring the downlink control channel onthe cell. The transitioning the cell to the dormancy comprises switchingan active bandwidth part of the cell to the dormant bandwidth part ofthe cell.

According to an example embodiment, the wireless device monitors adownlink control channel of a cell for the beam failure recoveryprocedure.

According to an example embodiment, the wireless device initiates thebeam failure recovery procedure in response to detecting a number ofbeam failure instances on the cell.

According to an example embodiment, the wireless device receives a MACCE indicating an activation of the cell. The wireless device activatesthe cell in response to the receiving the MAC CE.

According to an example embodiment, the wireless device receives one ormore radio resource control messages comprising configuration parametersof the cell comprising a plurality of bandwidth parts, the configurationparameters indicating one of the plurality of the bandwidth parts as thedormant bandwidth part of the cell.

According to an example embodiment, the wireless device receives a MACCE indicating a deactivation of the cell. The wireless devicedeactivates the cell in response to receiving the MAC CE indicating thedeactivation of the cell.

In an example, a wireless device may monitor one or more PDCCH of a cellin an active state. The wireless device may initiate a BFR procedure inresponse to detecting a number of beam failure instances on the cell.The wireless device may determine, in response to the initiating the BFRprocedure, no candidate beam is identified based on a threshold. Thewireless device may transmit a signal indicating no candidate beam isidentified. The wireless device may transition, in response to nocandidate beam being identified, the cell from the active state to adormant state. The wireless device, based on the transitioning to thedormant state, may stop monitoring, during a time duration, the one ormore PDCCHs on the cell, and transmit, during the time duration, CSIreports for the cell. In an example, the wireless device may monitor theone or more PDCCHs with a first monitoring periodicity. The wirelessdevice may monitor at least one of the one or more PDCCHs with a secondmonitoring periodicity in response to transitioning the cell to thedormant state. The wireless device may determine no candidate beam isidentified from a plurality of reference signals based on a channelquality, of none of the plurality of reference signals, being greaterthan the threshold. The wireless device may determine, in response tothe initiating the BFR procedure, at least one candidate beam isidentified based on the threshold. The wireless device may transmit asignal indicating the at least one candidate beam for the BFR procedure.The wireless device may maintain, in response to the at least onecandidate beam being identified, the cell in the active state. Based onthe cell in the active state, the wireless device may monitor the one ormore PDCCHs on the cell and transmit CSI reports for the cell.

In an example, a wireless device may initiate a BFR procedure inresponse to detecting a number of beam failure instances on a cell in anactive state. The wireless device may determine, in response to theinitiating the BFR procedure, no candidate beam is identified based on athreshold. The wireless device may transmit a signal indicating nocandidate beam is identified. The wireless device may receive a DCI as aresponse to the transmitting the signal. The wireless device maytransition, in response to the DCI, the cell from the active state todormant state. Based on the dormant state, the wireless device may stopmonitoring one or more PDCCHs on the cell and transmit CSI reports forthe cell. The DCI may not comprise an indication indicating a transitionof the cell from the active state to the dormant state.

In an example, a wireless device may receive, via a power saving channel(PSCH), a power saving indication (e.g., a wakeup indication or ago-to-sleep indication as shown in FIG. 26A and/or FIG. 26B. In responseto receiving the power saving indication indicating wakeup, the wirelessdevice may wake up to monitor PDCCH on a cell (a PCell or a SCell) innext DRX on duration of a DRX cycle as shown in FIG. 26A. In response toreceiving the power saving indication indicating go-to-sleep, thewireless device may skip monitoring PDCCH on a cell (a PCell or a SCell)in next DRX on duration of a DRX cycle as shown in FIG. 26B. Thewireless device may receive the power saving indication (e.g., comprisedin a DCI) at a time offset before a DRX on duration of a DRX cycle. Thewireless device, when skipping monitoring PDCCH on a cell in a DRX onduration, may continue CSI report on/for the cell in the DRX onduration. The wireless device may repeat monitoring the PSCH, forreceiving the power saving indication, of each DRX cycle.

In an example, when a SCell dormancy is supported, a wireless device mayreceive a first DCI indicating a transition of a SCell from an activestate to a dormant state. In response to receiving the indicationindicating the transition of the SCell to the dormant state, thewireless device may: skip PDCCH monitoring or reduce PDCCH monitoring onthe SCell, stop receiving PDSCH on the SCell, stop transmitting PUSCH onthe SCell, transmit CSI report for the SCell. In response to receivingthe indication indicating the transition of the SCell to the dormantstate, the wireless device may switch an active BWP of the SCell to asecond BWP of the SCell, the second BWP being configured for the dormantstate, or being the default BWP of the SCell. The wireless device maymaintain the dormant state of the SCell until receiving a second DCIindicating a transition of the SCell from the dormant state to theactive state. In response to receiving the second DCI, the wirelessdevice may transition the SCell from the dormant state to the activestate. When the SCell is in active state, the wireless device may:monitor PDCCH(s) on the SCell, receive transport blocks via PDSCH(s) ofthe SCell, transmit transport blocks via PUSCH(s) of the SCell, transmitCSI report for the SCell.

In existing technologies, a wireless device may monitor a power savingchannel for a power saving indication in a DRX off duration (e.g., whena DRX on duration timer is not running). After receiving the powersaving indication in the DRX off duration, the wireless device may startmonitoring PDCCH(s) on a next DRX on duration. In response to the powersaving indication indicating skipping PDCCH monitoring on the next DRXon duration, the wireless device may skip PDCCH monitoring on anactivated cell (e.g., PCell or SCell) and/or transmit CSI report on theactivated cell on the next DRX on duration.

In an example, a wireless device may receive a power saving indicationduring monitoring a power saving channel (e.g., DCI with CRC scrambledby a PS-RNTI, via a PDCCH), the power saving indication comprising awake-up indication and a SCell dormancy indication. The wake-upindication, comprising one bit set to a first value, may indicatemonitoring PDCCH on all cells in a DRX on duration of a next DRX cycle.The wake-up indication, when the bit set to a second value, may indicateskipping monitoring PDCCH on all cells in the DRX on duration of thenext DRX cycle. The SCell dormancy indication may indicate switching anactive BWP of a SCell to a dormant BWP of the SCell, when one or morebits of the SCell dormancy indication, associated with the SCell, is setto a first value. The SCell dormancy indication may indicate switchingfrom the dormant BWP of the cell to the active BWP of the SCell, whenone or more bits of the SCell dormancy indication, associated with theSCell, is set to a second value.

In an example, when receiving the wake-up indication and the SCelldormancy indication, the wireless device, by using existingtechnologies, may apply conflicting operations on one or more SCells.Applying the conflicting operation on the one or more SCells mayincrease power consumption of the wireless device and/or result inmisalignment a state of the SCell in a DRX operation between a basestation and the wireless device. There is a need to improve power savingmechanism and SCell dormancy mechanism. Example embodiments, bycombining and/or unifying the power saving mechanism and the SCelldormancy mechanism, may improve power consumption of a wireless deviceand improve SCell dormancy/activation transition latency. Exampleembodiments, by combining and/or unifying the power saving mechanism andthe SCell dormancy mechanism, may improve power consumption of awireless device in a DRX operation on the SCell.

One of example embodiment may comprise transmitting by a base station,and/or receiving by a wireless device, in a DRX off duration, a DCIindicating whether a wireless device shall perform a power savingoperation in a DRX on duration or transition a SCell between an activestate and a dormant state.

One of example embodiments may comprise transmitting by a base stationand/or receiving by a wireless device and in a DRX off duration, one ormore DCIs (with CRC scrambled by a PS-RNTI) comprising a wake-upindication and a SCell dormancy indication. The DRX off duration is anumber of symbols/slots before a DRX on duration of a DRX cycle, e.g.,based on example of FIG. 26A and/or FIG. 26B. Based on the embodiment, awireless device, by receiving the wake-up indication and the SCelldormancy indication in the one or more DCIs, may save the powerconsumption of the wireless device for blind decoding.

One of example embodiment may comprise determining a SCell transitionedto a dormancy as active state and not applying wake-up indication forPDCCH monitoring on the SCell in dormancy in response to receiving oneor more DCIs comprising a SCell dormancy indication and a wake-upindication. One of example embodiment may comprise determining a SCelltransitioned to a dormancy as active state and applying wake-upindication for CSI reporting on the SCell in dormancy in response toreceiving one or more DCIs comprising a SCell dormancy indication and awake-up indication. In an example, when the wake-up indication indicatesnot wake-up (e.g., skipping PDCCH monitoring) in the DRX on duration,the wireless device does not monitor PDCCH on the SCell in the dormancyduring the DRX on duration. When the wake-up indication indicateswake-up (e.g., monitoring PDCCH) in the DRX on duration, the wirelessdevice keeps the SCell in the dormancy (e.g., by not applying thewake-up indication on the SCell). The wireless device, by keeping theSCell in the dormancy, does not monitor PDCCH on the SCell during theDRX on duration. In an example, when the wake-up indication indicatesnot wake-up (e.g., skipping PDCCH monitoring) in the DRX on duration,the wireless device transmits CSI report for the dormant BWP of theSCell in the DRX on duration. Example embodiments may improve powerconsumption of a wireless device in a DRX operation on the SCell in adormancy.

FIG. 34 shows an example embodiment of a unified power saving operationand SCell dormancy transition. A wireless device may receive, from abase station, one or more RRC messages comprising first configurationparameters of power saving operations (or configurations) and secondconfiguration parameters of SCell dormancy operations (orconfigurations). The first configuration parameters of the power savingoperations may be implemented by example of FIG. 26A, FIG. 26B and/orFIG. 27 . The second configuration parameters of the SCell dormancyoperation may indicate a BWP of the SCell when transitioning to adormant state, a periodic CSI report configuration when transitioning tothe dormant state, and/or one or PDCCH configuration for the SCell inthe dormant state. The one or more PDCCH configuration may indicate oneor more search spaces/CORESETs on the SCell for PDCCH monitoring whentransitioning to the dormant state, one or more DCI format for the SCellin the dormant state.

As shown in FIG. 34 , the wireless device may receive a command (e.g.,an RRC message, a MAC CE, and/or a DCI) indicating an activation of theSCell. When configured with multiple SCells, the command may comprisemultiple indications, each indication associated with a SCell,indicating whether the SCell is activated. In response to the command,the wireless device may activate the SCell.

In an example, the wireless device may monitor, based on the firstconfiguration parameters, a PDCCH for receiving a DCI comprisingPS/dormancy indication at a first time before a DRX on duration, wherethe gap between the first time and a starting time of the DRX onduration may be configured in a RRC message, or predefined to a fixedvalue. The PDCCH may be a power saving channel based on the firstconfiguration parameters. The DCI may be CRC scrambled with a dedicatedRNTI for the PS/dormancy indication (e.g., PS-RNTI). The dedicated RNTImay be different from a C-RNTI.

In an example, the wireless device may receive the DCI comprising thePS/dormancy indication during monitoring the PDCCH in the DRX offduration. The wireless device may determine whether the PS/dormancyindication, in the DCI, indicate the wireless device shall perform apower saving operation, or indicate the wireless device shall perform aSCell dormancy transition.

In response to the PS/dormancy indication indicating the power savingoperation, the wireless device may skip PDCCH monitoring for the nextDRX on duration, on all activated cells (e.g., PCell, SCells.). Inresponse to the PS/dormancy indication indicating the power savingoperation, the wireless device may skip PDCCH monitoring for the nextDRX on duration, on one or more activated cells if the PS/dormancyindication comprise a PS indication bitmap. Each bit, of the bitmap,corresponding to one of the one or more activated cells, indicateswhether the wireless device shall skip PDCCH monitoring on the one ofthe one or more activated cells for the next DRX on duration. Inresponse to the PS/dormancy indication indicating the power savingoperation, the wireless device may continue CSI report for the SCell,the CSI report being configured for the SCell in the active state. Thewireless device may skip PDCCH monitoring and/or continue the CSI reportuntil the end of the DRX on duration. The wireless device may stop theCSI report in response to switching to a DRX off duration, e.g., basedon a DRX on duration timer expiring. The wireless device may repeat theprocess, for a next DRX cycle, comprising: monitoring the PDCCH forreceiving a PS/dormancy indication at time before a DRX on duration,skipping PDCCH monitoring and/or continuing CSI report in the DRX onduration if receiving the PS/dormancy indication indicating a powersaving operation, stopping CSI report in a DRX off duration.

In response to the PS/dormancy indication indicating the SCell dormancytransition, the wireless device may determine whether to transition anactivated SCell from an active state to a dormant state, or totransition from a dormant state to an active state. In response to thePS/dormancy indication indicating a transition of a SCell to a dormantstate, the wireless device may perform dormant actions for the SCellbased on the second configuration parameters, the dormant actionscomprising: stopping monitoring PDCCH on the SCell, stopping receivingPDSCH on the SCell, stopping transmitting uplink signals/channels (e.g.,PUSCH/PUCCH/SRS/PRACH) on the SCell, transmitting first CSI report forthe SCell in the dormant state. In response to the PS/dormancyindication indicating a transition of a SCell from a dormant state to anactive state, the wireless device may perform active actions for theSCell in the active state, the active actions comprising: monitoringPDCCH on the SCell, receiving PDSCH on the SCell, transmitting uplinksignals/channels (e.g., PUSCH/PUCCH/SRS/PRACH) on the SCell,transmitting second CSI report for the SCell in the active state. Thefirst CSI report for the SCell in the dormant state may be configuredwith a longer periodicity, and/or a smaller number of CSI quantities(e.g., PMI/CQI/RI/RSRP, and the like) than the second CSI report for theSCell in the active state. When configured with multiple active SCells,the PS/dormancy indication may comprise a PS/dormancy indication bitmap,each bit of the bitmap, corresponding to one SCell of the multipleactive SCells, indicating whether the wireless device shall transitionthe one SCell, of the multiple active SCells, to a dormant state, or anactive state. The wireless device may maintain a dormant state of aSCell or an active state of the SCell, after the SCell statetransitioning, until receiving another PS/dormancy indication indicatinganother SCell state transitioning.

In an example, the PS/dormancy indication in a DCI may be a one-bitindication, with a first value (e.g., 0) indicating a power savingoperation and a second value (e.g., 1) indicating a SCell dormancyoperation. In an example, the DCI may implicitly indicate whether thewireless device perform a power saving operation for a DRX cycle orperform a SCell state transition between dormant state and active state.The DCI, being CRC scrambled with a first RNTI, may indicate the powersaving operation for the DRX cycle. The DCI, being CRC scrambled with asecond RNTI, may indicate the SCell state transition. The DCI, beingtransmitted with a first DCI format, may indicate the power savingoperation for the DRX cycle. The DCI, being transmitted with a secondDCI format, may indicate the SCell state transition. The DCI, with oneor more fields being set to first predefined value, may indicate thepower saving operation for the DRX cycle. The DCI, with the one or morefields being set to second predefined value, may indicate the SCellstate transition. The one or more fields may comprise at least one of: afrequency resource indicator, a time resource indicator, a MCSindicator, a NDI, a HARQ process number, SRS indicator, CSI reportindicator, and the like.

FIG. 35 shows an example flowchart of a PS/dormancy operation. Awireless device may receive configuration parameters of a PS operationand a dormancy operation on a SCell. The wireless device may receive acommand (e.g., an RRC message, a MAC CE and/or a DCI) indicating anactivation of the SCell. The wireless device may activate the SCellbased on the command. In response to activating the SCell, the wirelessdevice may start a first CSI report for the SCell. The wireless devicemay monitor a PDCCH for receiving a PS/dormancy indication at a timebefore a DRX on duration of a DRX cycle. A DRX cycle may comprise a DRXon duration and a DRX off duration as shown in FIG. 24 . The wirelessdevice may receive the PS/dormancy indication during the monitoring thePDCCH at the time before the DRX on duration. The wireless device maydetermine whether to perform a power saving operation or to perform aSCell state transition between an active state and a dormant state. Inresponse to the PS/dormancy indication comprising a power savingindication, the wireless device may skip PDCCH monitoring on the DRX onduration of the DRX cycle, and/or continue the first CSI report. Inresponse to the PS/dormancy comprising a wake-up indication, thewireless device may monitor PDCCH on the SCell in the DRX on duration ofthe DRX cycle and continue the first CSI report. In response to thePS/dormancy indication indicating a SCell state transition from anactive state to a dormant state, the wireless device may skip PDCCHmonitoring on the SCell and transmit a second CSI report for the SCellin the dormant state. In response to the PS/dormancy indicationindicating a SCell state transition from a dormant state to an activestate, the wireless device may start PDCCH monitoring on the SCell andtransmit the first CSI report for the SCell in the active state. Thewireless device may maintain the state (dormant or active) of the SCelluntil receiving another PS/dormancy indication indicating SCell statetransitioning.

FIG. 36 shows an example of PS operation and SCell dormancy. In anexample, a wireless device may receive a command (e.g., an RRC message,a MAC CE and/or a DCI) indicating an activation of the SCell. Thewireless device may activate the SCell based on the command. In responseto activating the SCell, the wireless device may start a first CSIreport (e.g., periodic) for the SCell, the first CSI report beingconfigured for the SCell in active state. The wireless device maymonitor a PDCCH for receiving a first PS/dormancy indication at a firsttime. The wireless device may receive the first PS/dormancy indicationduring the monitoring the PDCCH. In response to the PS/dormancyindication indicating a SCell state transition from an active state to adormant state, the wireless device may transition the SCell into thedormant state. During a time period of the dormant state on the SCell,the wireless device may skip PDCCH monitoring on the SCell and transmita second CSI report for the SCell in the dormant state.

As shown in FIG. 36 , the wireless device may receive a secondPS/dormancy indication at a second time. The second PS/dormancyindication may comprise a wake-up indication. The wireless device maydetermine whether transition the SCell from the dormant state to anactive state, or maintain the SCell in the dormant state, based on thewake-up indication of the second PS/dormancy indication.

In an example, the wireless device may transition the SCell from thedormant state to an active state in response to the second PS/dormancyindication indicating a wake-up. The second PS/dormancy indication maynot indicate SCell state transition. In an example, the wireless devicemay transition the SCell from the dormant state to an active state whenthe wireless device determines the second PS/dormancy indicationoverwrite (or have higher priority than) the first PS/dormancyindication regarding a state (active state or dormant state) of a SCell.Example embodiments may improve downlink signal overhead for powersaving indication and dormancy indication.

In an example, the wireless device may maintain the SCell in the dormantstate, and/or monitor PDCCH(s) in a DRX on duration on one or moreactive cells (e.g., PCell or SCells) except the SCell in response to thesecond PS/dormancy indication indicating a wake-up. The secondPS/dormancy indication may not indicate SCell state transition. In anexample, the wireless device may maintain the SCell in the dormant statewhen the wireless device determines the second PS/dormancy indicationand the first PS/dormancy indication may be employed by the wirelessdevice independently or separately regarding a state (active state ordormant state) of a SCell. In an example, the wireless device maymaintain the SCell in the dormant state when the wireless devicedetermines the second PS/dormancy indication does not overwrite thefirst PS/dormancy indication regarding a state (active state or dormantstate) of a SCell.

In an example, a base station may transmit one or more RRC messagescomprising configuration parameters indicating whether a wireless deviceshall determine (consider, or treat) a SCell in a dormant state as anactivated SCell or as a deactivated SCell for a power saving operation.In an example, a base station and/or the wireless device may, determine(consider, or treat) a SCell in a dormant state as an active SCell, as apredefined rule, for the power saving operation. In an example, a basestation and/or the wireless device may, determine a SCell in a dormantstate as a deactivated SCell, as a predefined rule, for the power savingoperation.

In an example, a wireless device may determine a first SCell in adormant state as an activated SCell (e.g., with no or sparse PDCCHmonitoring). When receiving a power saving indication comprising awake-up indication, the wireless device may monitor the first SCell(e.g., with sparse PDCCH monitoring configured for a dormant state, orwith PDCCH monitoring configured for an active state) in a DRX onduration, based on determining the first SCell in the dormant state asan active SCell. When receiving power saving indication comprising ago-to-sleep indication, cross-slot scheduling, or maximum MIMO layersreduction indication for the first SCell, the wireless device may applythe power saving indication on the first SCell in the dormant state,e.g., by stopping sparse PDCCH monitoring, applying cross-slotscheduling, and/or applying the reduced maximum MIMO layers on theSCell, based on determining the first SCell in the dormant state as anactive SCell.

In an example, a wireless device may determine a first SCell in adormant state as a deactivated SCell. When receiving a power savingindication comprising a wake-up indication, the wireless device may skipmonitoring the first SCell and monitor other activated cells (e.g.,PCell or SCells) in a DRX on duration, based on determining the firstSCell in the dormant state as the deactivated SCell. When receivingpower saving indication comprising a go-to-sleep indication, cross-slotscheduling, or maximum MIMO layers reduction indication for the firstSCell, the wireless device may not apply the power saving indication onthe first SCell in the dormant state, e.g., by not applying cross-slotscheduling, not applying the reduced maximum MIMO layers on the firstSCell, based on determining the first SCell in the dormant state as thedeactivated SCell.

FIG. 37 shows an example embodiment of SCell dormancy management. In anexample, a wireless device may receive from a base station, one or moreRRC messages comprising configuration parameters of a plurality ofcells. The configuration parameters may indicate downlink controlchannel configuration parameters for receiving a DCI comprising awake-up indication for a DRX operation and a cell dormancy indication.In an example, the configuration parameter may indicate a PS-RNTI forreceiving the DCI. The configuration parameters may indicate controlchannel resource (e.g., time, frequency, beam, periodicity etc.) for thereception of the DCI.

In an example, the wireless device may receive a command (e.g., an RRCmessage, a MAC CE and/or a DCI) indicating an activation of a pluralityof SCells (e.g., 1st SCell and 2nd SCell). The wireless device mayactivate the plurality of SCells based on the command.

In response to activating a SCell (e.g., 1st SCell and 2nd SCell), thewireless device may start a CSI report (e.g., periodic) for the SCell,the CSI report being configured for the SCell in active state. Thewireless device may monitor a PDCCH on the SCell. The wireless devicemay receive downlink packet via the SCell and/or transmit uplink datapacket via the SCell, based on receiving a DCI during the monitoring thePDCCH on the SCell.

In an example, the wireless device may switch an active BWP of a SCellto a dormant BWP of the SCell based on receiving dormancy indication(s)(e.g., in a DRX on duration) indicating the switching (not shown in FIG.37 ). In an example, the wireless device may switch to a dormant BWP ofthe 1st SCell based on the dormancy indication(s). The wireless devicemay switch to a non-dormant BWP of the 2nd SCell based on the dormancyindication.

In an example, the wireless device may receive a DCI (with CRC scrambledby the PS-RNTI) comprising a wake-up indication and dormancyindication(s). The wireless device may receive the DCI in a time periodbefore a DRX on duration of a DRX cycle (e.g., as shown in FIG. 26Aand/or FIG. 26B).

In an example, in response to the cell dormancy indication(s) of the DCIindicating switching the 1st SCell to a non-dormant BWP of the 1stSCell, the wireless device may transition the 1st SCell to an activestate from a dormancy and/or switch from the dormant BWP of the 1stSCell to the non-dormant BWP of the 1st SCell. The dormant BWP and thenon-dormant BWP of the 1st SCell may be configured in the configurationparameters (e.g., in the one or more RRC messages above) of the 1stSCell. In an example, in response to the cell dormancy indication(s) ofthe DCI indicating switching the 2nd SCell to a dormant BWP of the 2ndSCell, the wireless device may transition the 2nd SCell to a dormancyfrom an active state and/or switch from the non-dormant BWP of the 2ndSCell to the dormant BWP of the 2nd SCell. The dormant BWP and thenon-dormant BWP of the 2nd SCell may be configured in the configurationparameters (e.g., in the one or more RRC messages above) of the 2ndSCell.

In an example, in response to the wake-up indication indicating PDCCHmonitoring for a DRX on duration, the wireless device, based on the 1stSCell in the active state (not in the dormancy), may apply the wake-upindication on the 1st SCell. In an example, the wireless device maymonitor PDCCH on the 1st SCell during the DRX on duration of the DRXcycle. The wireless device may skip PDCCH monitoring on the 1st SCellduring a DRX off duration of the DRX cycle.

In an example, in response to the wake-up indication indicating PDCCHmonitoring for a DRX on duration, the wireless device, based on the 2ndSCell in the dormancy, may keep the SCell in the dormancy and skip PDCCHmonitoring on the 2nd SCell in the DRX on duration of the DRX cycle. Thewireless device, based on the 2nd SCell in the dormancy, may not applythe wake-up indication on the 2nd SCell. Not applying the wake-upindication for PDCCH monitoring for a SCell in dormancy may improvepower consumption of a wireless device.

FIG. 38 shows an example flowchart of an embodiment. In an example, awireless device may receive from a base station one or more RRC messagescomprising configuration of a reception of a DCI comprising a wake-upindication and a cell dormancy indication. The one or more RRC messagesmay be implemented based on example of FIG. 37 . The wireless device mayreceive a command indicating an activation of the cell. The wirelessdevice may activate the cell based on the command. The wireless devicemay activate a first BWP of the cell in response to activating the cell.In an example, based on activating the first BWP, the wireless devicemay monitor PDCCH on the first BWP of the cell.

In an example, the wireless device may receive the DCI comprising awake-up indication and a cell dormancy indication. The wake-upindication may indicate a wake-up operation (e.g., PDCCH monitoring andCSI report) in a DRX on duration of a next DRX cycle. The wake-upindication may indicate a power saving operation (e.g., skipping PDCCHmonitoring and keeping CSI report) in a DRX on duration of a next DRXcycle.

In an example, based on receiving the cell dormancy indication, thewireless device may transition the cell to the dormancy, comprisingswitching from the first BWP to a dormant BWP of the cell. The wirelessdevice may stop PDCCH monitoring on the cell in the dormancy. Thewireless device may stop PDCCH monitoring on the cell in the dormancyregardless of whether the wake-up indication indicates the wake-upoperation or the power saving operation. In an example, based onreceiving the wake-up indication, the wireless device may apply the CSIreport operation associated with the wake-up indication on the cell inthe dormancy. In an example, in response to the wake-up indicationindicating the CSI report in the DRX on duration of the DRX cycle, thewireless device may transmit CSI report for the dormant BWP of the cellwhen the cell is in the dormancy. In an example, in response to thewake-up indication indicating PDCCH monitoring and the CSI report in theDRX on duration of the DRX cycle, the wireless device may skip PDCCHmonitoring on the cell in the dormancy and transmit CSI report for thedormant BWP of the cell in the dormancy.

FIG. 39 shows an example flowchart of an embodiment. At 3910, a wirelessdevice receives, based on PS-RNTI, one or more indications comprising awake-up indication indicating PDCCH monitoring during a DRX on durationof a DRX cycle and a cell dormancy indication indicating a switching toa dormant bandwidth part of a cell. At 3920, the wireless devicetransitions, based on the cell dormancy indication, the cell to thedormancy comprising switching to the dormant BWP of the cell. At 3930,based on transitioning the cell to the dormancy and the wake-upindication, the wireless device, during the DRX on duration, stopmonitoring downlink control channel on the cell, while maintaining thecell activated, and transmit CSI report for the dormant BWP of the cell.

According to an example embodiment, the wireless device may determinethe cell in an active state in response to the switching of the activebandwidth part of the cell to the dormant bandwidth part of the cell.

According to an example embodiment, the wireless device may receive theone or more indications in at least one DCI during a time period beforea start of the DRX on duration of a DRX cycle.

According to an example embodiment, the channel state information reportmay comprise one or more reference signal received power values of oneor more reference signal of the dormant bandwidth part of the cell. Thechannel state information report may be based on one or more referencesignals of the dormant bandwidth part of the cell. The channel stateinformation report may be configured on the dormant bandwidth part ofthe cell. The channel state information report may comprise a periodicchannel state information report transmitted in a plurality oftransmission occasions with a periodicity. The channel state informationreport may comprise a semi-persistent channel state information report,wherein the semi-persistent channel state information report istransmitted in a plurality of transmission occasions with a periodicityand/or the semi-persistent channel state information report is triggeredby a semi-persistent channel state report activation command.

According to an example embodiment, the wireless device may stopmonitoring the downlink control channel on the dormant bandwidth part ofthe cell.

According to an example embodiment, the wireless device may receive oneor more downlink control information, comprising the one or moreindications, with CRC bits being scrambled by a PS-RNTI.

According to an example embodiment, in response to a second cell beingin a deactivated state, during the DRX on duration, the wireless devicemay skip monitoring downlink control channel on the second cell and skiptransmitting channel state information report for the second cell.

According to an example embodiment, the cell is a secondary cell of aplurality of cells comprising a primary cell and a second cell.

According to an example embodiment, the wireless device may receive oneor more radio resource control (RRC) messages comprising configurationparameters of the plurality of cells. The wireless device may receive aMAC CE indicating an activation of the cell. The wireless device mayactivate the cell, in response to receiving the MAC CE, comprisingactivating a first bandwidth part of the cell as an active bandwidthpart, wherein the first bandwidth part is different from the dormantbandwidth part and monitoring downlink control channels on the firstbandwidth part of the cell.

According to an example embodiment, the wireless device may receive froma base station, one or more RRC messages comprising configurationparameters of the cell, the configuration parameters indicating thedormant BWP of a plurality of BWPs of the cell. The configurationparameters may comprise a PS-RNTI for receiving one or more downlinkcontrol information comprising the one or more indications. Theconfiguration parameters may indicate that no downlink control channelresource is configured on the dormant bandwidth part of the cell. Theconfiguration parameters may indicate that no search space is configuredon the dormant bandwidth part of the cell. The one or more RRC messagesmay comprise second configuration parameters of a DRX operation, whereinthe second configuration parameters of the DRX operation comprise: alength of the DRX cycle, a starting offset of the DRX cycle and a lengthof the DRX on duration of the DRX cycle. The one or more RRC messagesmay comprise third configuration parameters of the power savingoperation, wherein the third configuration parameters of the powersaving operation comprise a time offset indicating a starting symbol,for monitoring downlink control channels for receiving one or moredownlink control information comprising the one or more indications,relative to a start of the DRX on duration of the DRX cycle.

According to an example embodiment, the wireless device may receive aMAC CE indicating a deactivation of the cell. The wireless device maydeactivate the cell in response to the receiving the MAC CE indicatingthe deactivation of the cell. In response to deactivating the cell, thewireless device may stop transmitting the channel state informationreport for the dormant bandwidth part of the cell.

According to an example embodiment, the one or more indications mayfurther comprise a second cell dormancy indication indicating atransition of a second cell from a dormancy to an active state. Thewireless device may transition, based on the second cell dormancyindication, the second cell from the dormancy to the active state,wherein the transitioning the second cell from the dormancy to theactive state comprises switching from a dormant bandwidth part of thesecond cell to a second bandwidth part of the second cell. In anexample, one or more RRC messages may comprise configuration parametersindicating one of a plurality of bandwidth parts of the second cell asthe second bandwidth part of the second cell. Based on transitioning thesecond cell to the active state and the wake-up indication, during theDRX on duration, the wireless device may monitor downlink controlchannel on the second cell and transmit channel state information reportfor the second bandwidth part of the second cell. The channel stateinformation report for the second cell may be based on one or morereference signals of the second bandwidth part of the second cell. Thewireless device may monitor the downlink control channel on the secondbandwidth part of the second cell. The wireless device may receive asecond DCI during the monitoring the downlink control channel on thesecond bandwidth part of the second cell. The wireless device maytransmit an uplink TB based on the second DCI indicating an uplinkgrant. The wireless device may receive a downlink TB based on the secondDCI indicating a downlink assignment.

What is claimed is:
 1. A method comprising: transmitting, by a basestation to a wireless device, indications comprising: a wake-upindication indicating downlink control channel monitoring, for aplurality of cells, during a discontinuous reception (DRX) on durationof a DRX cycle; and a dormancy indication indicating a switching to adormant bandwidth part of a cell, from the plurality of cells, to stopdownlink control channel monitoring; and during the DRX on duration andbased on transmitting both the wake-up indication and the dormancyindication: stopping transmitting a downlink control channel on thecell, while maintaining the cell activated; and receiving a channelstate information report for the dormant bandwidth part.
 2. The methodof claim 1, wherein the cell is maintained in an active state after theswitching from an active bandwidth part of the cell to the dormantbandwidth part of the cell.
 3. The method of claim 1, wherein theindications are transmitted in at least one downlink control information(DCI) during a DRX off duration, and wherein the DRX off duration is notin the DRX on duration.
 4. The method of claim 1, wherein the stoppingtransmitting the downlink control channel is on the dormant bandwidthpart of the cell.
 5. The method of claim 1, further comprisingtransmitting one or more downlink control information (DCI), comprisingthe indications, with cyclic redundancy check bits being scrambled by apower saving radio network temporary identifier.
 6. The method of claim1, further comprising: transmitting, to the wireless device, one or moreradio resource control (RRC) messages comprising: configurationparameters of the cell, the configuration parameters indicating thedormant bandwidth part of a plurality of bandwidth parts of the cell;and a time offset indicating a starting symbol, for transmittingdownlink control channels comprising one or more downlink controlinformation comprising the indications, relative to a start of the DRXon duration of the DRX cycle.
 7. The method of claim 1, furthercomprising: transmitting a medium access control control element (MACCE) message indicating a deactivation of the cell; deactivating the cellafter the transmitting the MAC CE message indicating the deactivation ofthe cell; and stopping receiving the channel state information reportfor the dormant bandwidth part of the deactivated cell.
 8. A basestation comprising: one or more processors; and memory storinginstructions that, when executed by the one or more processors, causethe base station to: transmit, to a wireless device, indicationscomprising: a wake-up indication indicating downlink control channelmonitoring, for a plurality of cells, during a discontinuous reception(DRX) on duration of a DRX cycle; and a dormancy indication indicating aswitching to a dormant bandwidth part of a cell, from the plurality ofcells, to stop downlink control channel monitoring; and during the DRXon duration and based on transmitting both the wake-up indication andthe dormancy indication: stop transmitting a downlink control channel onthe cell, while maintaining the cell activated; and receive a channelstate information report for the dormant bandwidth part.
 9. The basestation of claim 8, wherein the cell is maintained in an active stateafter the switching from an active bandwidth part of the cell to thedormant bandwidth part of the cell.
 10. The base station of claim 8,wherein the indications are transmitted in at least one downlink controlinformation (DCI) during a DRX off duration, and wherein the DRX offduration is not in the DRX on duration.
 11. The base station of claim 8,wherein the stopping transmitting the downlink control channel is on thedormant bandwidth part of the cell.
 12. The base station of claim 8,wherein the instructions, when executed by the one or more processors,further cause the base station to transmit one or more downlink controlinformation (DCI), comprising the indications, with cyclic redundancycheck bits being scrambled by a power saving radio network temporaryidentifier.
 13. The base station of claim 8, wherein the instructions,when executed by the one or more processors, further cause the basestation to: transmit, to the wireless device, one or more radio resourcecontrol (RRC) messages comprising: configuration parameters of the cell,the configuration parameters indicating the dormant bandwidth part of aplurality of bandwidth parts of the cell; and a time offset indicating astarting symbol, for transmitting downlink control channels comprisingone or more downlink control information comprising the indications,relative to a start of the DRX on duration of the DRX cycle.
 14. Thebase station of claim 8, wherein the instructions, when executed by theone or more processors, further cause the base station to: transmit amedium access control control element (MAC CE) message indicating adeactivation of the cell; deactivate the cell after the transmitting theMAC CE message indicating the deactivation of the cell; and stopreceiving the channel state information report for the dormant bandwidthpart of the deactivated cell.
 15. A non-transitory computer-readablemedium comprising instructions that, when executed by one or moreprocessors of a base station, cause the base station to: transmit, to awireless device, indications comprising: a wake-up indication indicatingdownlink control channel monitoring, for a plurality of cells, during adiscontinuous reception (DRX) on duration of a DRX cycle; and a dormancyindication indicating a switching to a dormant bandwidth part of a cell,from the plurality of cells, to stop downlink control channelmonitoring; and during the DRX on duration and based on transmittingboth the wake-up indication and the dormancy indication: stoptransmitting a downlink control channel on the cell, while maintainingthe cell activated; and receive a channel state information report forthe dormant bandwidth part.
 16. The non-transitory computer-readablemedium of claim 15, wherein the cell is maintained in an active stateafter the switching from an active bandwidth part of the cell to thedormant bandwidth part of the cell.
 17. The non-transitorycomputer-readable medium of claim 15, wherein the indications aretransmitted in at least one downlink control information (DCI) during aDRX off duration, and wherein the DRX off duration is not in the DRX onduration.
 18. The non-transitory computer-readable medium of claim 15,wherein the stopping transmitting the downlink control channel is on thedormant bandwidth part of the cell.
 19. The non-transitorycomputer-readable medium of claim 15, wherein the instructions, whenexecuted by the one or more processors, further cause the base stationto transmit one or more downlink control information (DCI), comprisingthe indications, with cyclic redundancy check bits being scrambled by apower saving radio network temporary identifier.
 20. The non-transitorycomputer-readable medium of claim 15, wherein the instructions, whenexecuted by the one or more processors, further cause the base stationto: transmit, to the wireless device, one or more radio resource control(RRC) messages comprising: configuration parameters of the cell, theconfiguration parameters indicating the dormant bandwidth part of aplurality of bandwidth parts of the cell; and a time offset indicating astarting symbol, for transmitting downlink control channels comprisingone or more downlink control information comprising the indications,relative to a start of the DRX on duration of the DRX cycle.